angular/packages/core/test/bundling
Angular Robot 78c417ace1 build: update cross-repo angular dependencies (#61910)
See associated pull request for more information.

PR Close #61910
2025-06-06 10:30:47 +02:00
..
animations-standalone refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
cyclic_import build: adjust bundling tests to use Angular CLI (#61566) 2025-05-29 14:39:11 -04:00
defer refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
forms_reactive refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
forms_template_driven refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
hydration refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
image-directive build: migrate all ng_module in packages/core/test (#61472) 2025-05-20 10:00:43 +00:00
router refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
standalone_bootstrap refactor(platform-browser): drop isPlatformServer in SharedStylesHost (#61685) 2025-06-05 14:53:35 +02:00
BUILD.bazel build: adjust bundling tests to use Angular CLI (#61566) 2025-05-29 14:39:11 -04:00
package.json build: update cross-repo angular dependencies (#61910) 2025-06-06 10:30:47 +02:00
README.md build: adjust bundling tests to use Angular CLI (#61566) 2025-05-29 14:39:11 -04:00

Bundle

js_expected_symbol_test

This folder contains tests which assert that most of the code is tree shaken away. This is asserted by keeping gold files of all symbols which are expected to be retained. When doing renaming it is often necessary to update the gold files; to do so use these scripts:

yarn run symbol-extractor:check
yarn run symbol-extractor:update

Debugging

You can inspect the build output of each project by building the :bundles target.

yarn bazel build //packages/core/test/bundling/standalone_bootstrap:bundles

This output is always unmangled and can be easily used for debugging. Alternatively, you can also serve the output by running:

yarn bazel run //packages/core/test/bundling/standalone_bootstrap:bundles.serve

If needed, you can also control the Angular CLI optimizations via environment variables that you can set via the env attribute in BUILD.bazel of each test.