mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
Paul Gschwendtner
e910893fa6
Instead of dev-infra maintaining a custom ESBuild + Terser pipeline that tries to emulate the Angular CLI, we are switching the bundling core tests to a new rule that really leverages the Angular CLI. This involves some file renames and small adjustments. In addition, we leverage the updated symbol tracking rule to output new goldens that can work with multiple bundle files (as generated by the Angular CLI; especially with defer and its "lazy" chunks).
951 B
951 B
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:
yarn run symbol-extractor:check
yarn run symbol-extractor:update
Debugging
You can inspect the build output of each project by building the :bundles target.
yarn 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:
yarn 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.