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

PR Close #63179
2025-08-15 11:41:02 +02:00
..
animations-standalone refactor(animations): optimize resolveTimeExpression (#62927) 2025-08-06 15:09:18 +02:00
cyclic_import build: remove ts_project_interop infrastructure (#62908) 2025-07-31 09:12:58 +00:00
defer fix(core): fixes empty animations when recalculating styles (#63007) 2025-08-06 11:17:30 +02:00
forms_reactive refactor(core): this delays removal of stylesheets when the element registry is present (#62943) 2025-08-01 12:54:22 +00:00
forms_template_driven refactor(core): this delays removal of stylesheets when the element registry is present (#62943) 2025-08-01 12:54:22 +00:00
hydration refactor(core): this delays removal of stylesheets when the element registry is present (#62943) 2025-08-01 12:54:22 +00:00
image-directive build: update to bazel 7.6.0 (#63096) 2025-08-14 13:01:32 +02:00
router fix(router): attempt to resolve component resources in JIT mode (#63062) 2025-08-08 14:18:21 -07:00
standalone_bootstrap refactor(core): this delays removal of stylesheets when the element registry is present (#62943) 2025-08-01 12:54:22 +00:00
BUILD.bazel build: update to the latest version of devinfra and rename npm2 workspace (#63093) 2025-08-11 10:35:34 -07:00
package.json build: update cross-repo angular dependencies (#63179) 2025-08-15 11:41:02 +02:00
README.md build: use pnpm as the package manager instead of yarn (#62924) 2025-07-31 22:06:27 +00: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.