angular/packages/core/test/bundling
Alan Agius 64e28ccf81 build: update cross-repo angular dependencies (#64073)
See associated pull request for more information.

Closes #64043 as a pr takeover

PR Close #64073
2025-09-25 10:26:19 -04:00
..
animations-standalone refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00:00
cyclic_import build: rename defaults2.bzl to defaults.bzl (#63383) 2025-08-25 15:45:01 -07:00
defer refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00:00
forms_reactive build: update cross-repo angular dependencies (#63902) 2025-09-18 14:39:51 +00:00
forms_template_driven build: update cross-repo angular dependencies (#63902) 2025-09-18 14:39:51 +00:00
hydration refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00:00
image-directive refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00:00
router refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00:00
standalone_bootstrap refactor: clean up explicit standalone flags from tests (#63963) 2025-09-22 14:27:34 +00: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 (#64073) 2025-09-25 10:26:19 -04: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.