denoland/deno · error
native tsc exited with {} without parseable diagnostics{}
Error message
native tsc exited with {} without parseable diagnostics{} What it means
Error "native tsc exited with {} without parseable diagnostics{}" thrown in denoland/deno.
Source
Thrown at cli/tools/check.rs:395
log::error!("{}\n", diagnostics);
return Err(deno_core::anyhow::anyhow!("Type checking failed."));
}
// tsc exited non-zero but we have nothing to show. If it printed diagnostic
// lines we deliberately dropped (e.g. `noImplicitOverride` in remote modules),
// its exit code is expected - treat the check as clean. Only when tsc produced
// no recognizable diagnostics at all is this a genuine failure (an internal
// error or a malformed generated config); surface whatever it printed then.
let tsc_reported_diagnostics =
crate::tsc::native::output_has_diagnostics(&stdout);
if !output.status.success() && !tsc_reported_diagnostics {
let detail = stdout.trim();
let detail = if detail.is_empty() {
stderr.trim()
} else {
detail
};
return Err(deno_core::anyhow::anyhow!(
"native tsc exited with {} without parseable diagnostics{}",
output.status,
if detail.is_empty() {
String::new()
} else {
format!(":\n{detail}")
}
));
}
// Type-checked clean: record the hash so an unchanged re-check skips tsc.
if let Some(check_hash) = maybe_check_hash {
type_check_cache.add_check_hash(check_hash);
}
Ok(())
}
View on GitHub (pinned to 89f33cbef2)
When it happens
Trigger: Thrown at cli/tools/check.rs:395 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/f97dc2c4036a3abc.
Report an issue: GitHub.