angular/packages/core/test/bundling
Matthieu Riegler 10bdae9098 build: enable angular formatting on all html files
This should also be safe on any html file that isn't an angular template

(cherry picked from commit 9d1d742f1b)
2025-12-08 10:19:50 -08:00
..
animations-standalone fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:23 -05:00
create_component perf(core): tree shake unused dynamic [field] binding instructions (#65599) 2025-12-03 15:10:50 +01:00
cyclic_import build: format md files 2025-11-06 10:07:13 -08:00
defer fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:23 -05:00
forms_reactive fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:23 -05:00
forms_template_driven fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:23 -05:00
hydration refactor: replace getDocument() with inject(DOCUMENT) 2025-11-25 13:05:01 -05:00
image-directive build: enable angular formatting on all html files 2025-12-08 10:19:50 -08:00
router Revert "refactor(router): compress synchronous end to router navigation to single operator" 2025-12-02 19:13:07 +01:00
standalone_bootstrap fix(core): use injected DOCUMENT for CSP_NONCE 2025-11-25 11:39:23 -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-12-04 11:26:14 -08:00
README.md build: format md files 2025-11-06 10:07:13 -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.