mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
760b1f3d0b
Currently when the extended type check fails due to an import reference that cannot be generated, the fatal diagnostic is not caught and not properly exposed as a `ts.Diagnostic` that can be gracefully handled. This is inconsistent to non-extended type checking diagnostics. This is problematic because Angular CLI applications currently fail in obscure ways because: - the CLI does not expect `getDiagnosticsForFile` to actually throw runtime errors. - the CLI does not seem to properly print these errors given the parallel workers and build excection, and those errors are especially hard to debug because there is no `stack` for `FatalDiagnosticError`'s. Example: `MyDir` is not exported and the type check block cannot reference it. PR Close #53896 |
||
|---|---|---|
| .. | ||
| integrationtest | ||
| linker | ||
| ngcc | ||
| private | ||
| src | ||
| test | ||
| BUILD.bazel | ||
| esbuild.config.js | ||
| index.ts | ||
| package.json | ||
| tsconfig-build.json | ||
| tsconfig.json | ||