angular/packages/core/test/bundling
Angular Robot 05d9b97cf9 build: update cross-repo angular dependencies
See associated pull request for more information.
2026-04-09 14:17:44 +03:00
..
animations-standalone fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
create_component fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
cyclic_import build: format md files 2025-11-06 10:03:05 -08:00
defer fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
forms_reactive fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
forms_template_driven fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
hydration fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07:00
image-directive fix(common): fix LCP image detection with duplicate URLs 2026-02-20 21:23:27 +00:00
router fix(core): treat object[data] as resource URL context (#67797) 2026-04-01 11:43:59 +02:00
standalone_bootstrap fix(core): reverts "feat(core): add support for nested animations" 2026-03-12 09:58:07 -07: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 2026-04-09 14:17:44 +03: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.