Currently, ngtsc decides to use remote scoping if the compilation of a component may create a cyclic import. This happens if there are two components in a scope (say, A and B) and A directly uses B. During compilation of B ngtsc will then note that if B were to use A, a cycle would be generated, and so it will opt to use remote scoping for B. ngtsc already uses the R3TargetBinder to correctly track the imports that are actually required, for future cycle tracking. This commit expands that usage to not trigger remote scoping unless B actually does consume A in its template. PR Close #29404
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871)
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871)
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871)
Angular
Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.
Languages
TypeScript
68.6%
HTML
12.8%
JavaScript
8.4%
Pug
7%
Starlark
1.4%
Other
1.7%