angular/packages/core/test/bundling
Andrew Scott 1ab461c846 refactor(router): Store route injector on ActivatedRoute instance
This eliminates the need to pass around the EnvironmentInjector
everywhere we need the injection context for a route.
2025-11-20 17:05:10 -05:00
..
animations-standalone refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
cyclic_import build: format md files 2025-11-06 10:03:05 -08:00
defer refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
forms_reactive refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
forms_template_driven refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
hydration refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
image-directive build: format md files 2025-11-06 10:03:05 -08:00
router refactor(router): Store route injector on ActivatedRoute instance 2025-11-20 17:05:10 -05:00
standalone_bootstrap refactor(core): export profile event as enum and move profile_types.ts and framework to shared devtools folder 2025-11-19 15:22:49 -08:00
BUILD.bazel build: update to the latest version of devinfra and rename npm2 workspace (#63093) 2025-08-11 10:35:32 -07:00
package.json build: update cross-repo angular dependencies 2025-11-19 15:00:49 -08:00
README.md build: format md files 2025-11-06 10:03:05 -08: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:

pnpm run symbol-extractor:check
pnpm run symbol-extractor:update

Debugging

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

pnpm 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:

pnpm 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.