Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/packages/core/test/bundling
History
Kristiyan Kostadinov 6b5e6b7ff7 refactor(compiler): always generate DOM-only templates for blocks (#62096) 
Block templates can't have directives so we can always generate them as DOM-only.

PR Close #62096
2025-06-23 14:24:09 +02:00
..
animations-standalone refactor(compiler): always generate DOM-only templates for blocks (#62096) 2025-06-23 14:24:09 +02:00
cyclic_import build: fix hermetic execution of packages/core/test/... (#62027) 2025-06-12 12:16:56 +02:00
defer refactor(compiler): always generate DOM-only templates for blocks (#62096) 2025-06-23 14:24:09 +02:00
forms_reactive build: fix hermetic execution of packages/core/test/... (#62027) 2025-06-12 12:16:56 +02:00
forms_template_driven build: fix hermetic execution of packages/core/test/... (#62027) 2025-06-12 12:16:56 +02:00
hydration build: migrate packages/core/test to new jasmine_test rule (#61902) 2025-06-12 10:00:09 +02:00
image-directive refactor: use zone.js from npm instead of packages/zone.js throughout repo (#61977) 2025-06-10 12:02:03 -07:00
router refactor(compiler): always generate DOM-only templates for blocks (#62096) 2025-06-23 14:24:09 +02:00
standalone_bootstrap build: migrate packages/core/test to new jasmine_test rule (#61902) 2025-06-12 10:00:09 +02:00
BUILD.bazel build: adjust bundling tests to use Angular CLI (#61566) 2025-05-29 14:39:11 -04:00
package.json build: update cross-repo angular dependencies (#62079) 2025-06-19 10:12:19 +02:00
README.md build: adjust bundling tests to use Angular CLI (#61566) 2025-05-29 14:39:11 -04:00

README.md

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.