Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/integration/ng-modules-importability
History
Joey Perrott 32c00ab416 build: standardize usage of js_binary (#62860) 
Remove usages of nodejs_binary and use a commonly defined js_binary macro

PR Close #62860
2025-07-29 06:43:44 +02:00
..
BUILD.bazel build: replace all ng_package with new rule from rules_angular (#61843) 2025-06-04 09:13:41 +00:00
find-all-modules.mts build: migrate integration and primitives/defer to ts_project (#61843) 2025-06-04 09:13:41 +00:00
index.bzl build: standardize usage of js_binary (#62860) 2025-07-29 06:43:44 +02:00
index.mts build: replace all ng_package with new rule from rules_angular (#61843) 2025-06-04 09:13:41 +00:00
README.md test: add integration test to ensure all exported modules can be imported (#60489) 2025-03-20 12:32:36 -07:00
tsconfig.json build: replace all ng_package with new rule from rules_angular (#61843) 2025-06-04 09:13:41 +00:00

README.md

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.