xai-org/grok-build · error

npm view @{} failed: {}

Error message

npm view @{} failed: {}

What it means

fetch_npm_tag runs `npm view <pkg>@<tag> --json` (detached, with pager disabled) and reads its JSON stdout. If the npm process exits non-zero, the function bails with the tag and the trimmed stderr, so npm's own diagnostic (network error, 404, auth failure) is embedded in this error message.

Source

Thrown at crates/codegen/xai-grok-update/src/version.rs:192

        NPM_PACKAGE.to_string()
    } else {
        format!("{}@{}", NPM_PACKAGE, tag)
    };
    let mut args = vec!["view", &pkg_spec, "version", "--json"];
    let registry_flag;
    if let Some(registry) = npm_registry {
        registry_flag = format!("--registry={}", registry);
        args.push(&registry_flag);
    }
    let mut cmd = Command::new("npm");
    cmd.args(&args).stdin(std::process::Stdio::null());
    xai_grok_tools::util::detach_command(&mut cmd);
    cmd.envs(xai_grok_tools::util::pager_env());
    let output = cmd.output().await?;

    if !output.status.success() {
        let stderr = String::from_utf8_lossy(&output.stderr);
        anyhow::bail!("npm view @{} failed: {}", tag, stderr.trim());
    }

    let stdout = String::from_utf8(output.stdout)?;
    let value: Value = serde_json::from_str(stdout.trim())?;
    match value {
        Value::String(version) => Ok(version),
        Value::Array(values) => values
            .iter()
            .rev()
            .find_map(|entry| entry.as_str().map(|item| item.to_string()))
            .ok_or_else(|| anyhow::anyhow!("npm view @{} returned empty version list", tag)),
        _ => anyhow::bail!("npm view @{} returned unexpected JSON", tag),
    }
}

/// Fetch the latest version from GitHub Releases using `gh release list`.
/// For alpha channel, fetches both pre-release and stable-only, returns the
/// semver-greater — `gh release list --limit 1` orders by publication date,

View on GitHub (pinned to bc7f02eddd)

Solutions

1. Inspect the stderr embedded in the message — it contains npm's actual cause (ENOTFOUND, 404, E401, etc.)
2. Verify network/registry access: run `npm view <pkg>@<tag>` manually and check .npmrc registry/proxy settings
3. Confirm the package name and dist-tag exist on the registry (npm view <pkg> versions)
4. For private registries, run npm login or configure credentials; ensure npm is installed and on PATH

Example fix

// before (no registry access)
npm view @xai/grok@latest  -> ENOTFOUND registry.npmjs.org
// after: point npm at the reachable registry and retry
npm config set registry https://registry.npmjs.org/
# or set proxy: npm config set proxy http://proxy.corp:8080

// Preflight: ensure npm exists and the registry is reachable before calling fetch_npm_tag
which::"npm".ok_or("npm not found on PATH")?;
let ok = std::process::Command::new("npm")
    .args(["ping"])
    .output()
    .map(|o| o.status.success())
    .unwrap_or(false);
if !ok { eprintln!("npm registry unreachable; fix network/.npmrc before updating"); }

// Retry transient npm failures with backoff; surface stderr for permanent ones
for attempt in 0..3 {
    match fetch_npm_version(tag).await {
        Ok(v) => break Ok(v),
        Err(e) if e.to_string().contains("npm view") && is_transient(&e) && attempt < 2 => {
            tokio::time::sleep(Duration::from_secs(2u64.pow(attempt))).await;
        }
        Err(e) => break Err(e),
    }
}

When it happens

Trigger: Any non-zero exit of the underlying `npm view` command in fetch_npm_tag — e.g. the package@tag does not exist, npm is missing or not on PATH, the registry is unreachable, a proxy blocks the request, or auth is required for a private package. Called via fetch_npm_version and fetch_npm_tag_for_test.

Common situations: Offline/VPN/CI environment without registry access; typo'd package name or tag (latest/alpha); corporate proxy or custom registry misconfiguration; private registry requiring login (npm login); npm not installed in container images.

Related errors

• npm view @{} returned empty version list
• send failed: {body}
• screen query failed: {body}
• resize failed: {body}
• wait failed: {body}

AI-assisted analysis of xai-org/grok-build@bc7f02eddd (2026-08-31). Data as JSON: /api/errors/1a4b66163eb2bb6a. Report an issue: GitHub.