angular/packages/core/test/bundling
Leon Senft e6d5632a30 perf(core): tree shake unused dynamic [field] binding instructions (#65599)
Move the instructions used to dynamically bind a `Field` directive to a
form control onto the `Field` itself. This way the instructions are only
retained if the app uses the `Field` directive.

PR Close #65599
2025-12-03 15:10:49 +01:00
..
animations-standalone fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:20 -05:00
create_component perf(core): tree shake unused dynamic [field] binding instructions (#65599) 2025-12-03 15:10:49 +01:00
cyclic_import build: format md files 2025-11-06 10:03:05 -08:00
defer fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:20 -05:00
forms_reactive fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:20 -05:00
forms_template_driven fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:20 -05:00
hydration refactor: replace getDocument() with inject(DOCUMENT) 2025-11-25 13:04:58 -05:00
image-directive build: format md files 2025-11-06 10:03:05 -08:00
router refactor(router): Clean up cancellation event handling 2025-12-02 16:45:17 +01:00
standalone_bootstrap fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:20 -05: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-26 15:50:56 -05: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.