angular/integration/ng-modules-importability
Paul Gschwendtner 87751c0796 test: ng-modules-importability test should import every module in isolation (#60503)
This will make the test even more useful, as it ensures that we aren't
accidentally relying on the compiler potentially discovering best
guessed modules from other imports that previously were part of the same
file (importing all modules as part of the test).

PR Close #60503
2025-03-21 14:36:27 -07:00
..
BUILD.bazel test: ng-modules-importability test should import every module in isolation (#60503) 2025-03-21 14:36:27 -07:00
find-all-modules.ts test: add integration test to ensure all exported modules can be imported (#60489) 2025-03-20 12:32:36 -07:00
index.bzl test: ng-modules-importability test should import every module in isolation (#60503) 2025-03-21 14:36:27 -07:00
index.ts test: ng-modules-importability test should import every module in isolation (#60503) 2025-03-21 14:36:27 -07:00
README.md test: add integration test to ensure all exported modules can be imported (#60489) 2025-03-20 12:32:36 -07:00

This test is a safety check, ensuring that all @NgModule's exported by Angular framework packages can be imported in user code without causing any build errors.

Occasionally, an @NgModule might re-export another module. This is fine, but there are cases, especially with relative imports being used, where the compiler (in consuming projects) is not able to find a working import to these re-exported symbols.

The re-exported symbols simply need to be re-exported from the entry-point. For more details on this, see: https://github.com/angular/components/pull/30667.