4f42de9704
ngcc computes a dependency graph of entry-points to ensure that entry-points are processed in the correct order. Previously only the imports in source files were analysed to determine the dependencies for each entry-point. This is not sufficient when an entry-point has a "type-only" dependency - for example only importing an interface from another entry-point. In this case the "type-only" import does not appear in the source code. It only appears in the typings files. This can cause a dependency to be missed on the entry-point. This commit fixes this by additionally processing the imports in the typings program, as well as the source program. Note that these missing dependencies could cause unexpected flakes when running ngcc in async mode on multiple processes due to the way that ngcc caches files when they are first read from disk. Fixes #34411 // FW-1781 PR Close #34494 |
||
|---|---|---|
| .. | ||
| commonjs_dependency_host_spec.ts | ||
| dependency_resolver_spec.ts | ||
| esm_dependency_host_spec.ts | ||
| module_resolver_spec.ts | ||
| umd_dependency_host_spec.ts | ||