denoland/deno · error

Failed to generate tsconfig: {e}

Error message

Failed to generate tsconfig: {e}

What it means

Error "Failed to generate tsconfig: {e}" thrown in denoland/deno.

Source

Thrown at cli/tools/installer/npm_compat.rs:875

    project_root,
    deno_compiler_options,
    resolved_compiler_options,
    deno_imports,
    // Command-line roots scope graph/dependency discovery only. Keep the
    // generated project open so bundlers can consume its resolver mappings for
    // any entrypoint they are asked to bundle.
    &[],
    http_modules,
    member_paths,
    jsr_packages_dir,
    npm_package_paths,
    npm_project_references,
    node_types_root,
    excludes,
    has_local_wasm,
    manage_root_tsconfig,
  )
  .map_err(|e| anyhow!("Failed to generate tsconfig: {e}"))?;

  log::debug!("Generated {}", generated.tsconfig_path.display());

  Ok(())
}

/// Install jsr: compatibility packages by downloading from npm.jsr.io.
///
/// Uses `HttpClient::download` directly (not `CliFileFetcher`) because we
/// don't want each registry/tarball URL surfacing as a user-visible
/// "Download …" line in `deno install` output — those are an
/// implementation detail of the stock-tsc compatibility setup. The
/// fetcher's caching and redirect handling are unnecessary for npm.jsr.io.
async fn install_jsr_packages(
  jsr_packages_dir: &Path,
  deno_imports: Option<&Value>,
  http_client: &HttpClient,
) -> Result<Vec<InstalledJsrPackage>, AnyError> {

View on GitHub (pinned to 89f33cbef2)

When it happens

Trigger: Thrown at cli/tools/installer/npm_compat.rs:875 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of denoland/deno@89f33cbef2 (2026-08-16). Data as JSON: /api/errors/127440b83ae95e7a. Report an issue: GitHub.