fa3689f432
One of the main goals of the bundling tests is to verify that unused symbols are tree-shaken away in prod bundles. Currently both Reactive and Template-driven test apps are merged into one. In order to make these tree-shaking tests even more useful, this commit splits exiting test app into two, so that we can further optimize sets of symbols that should be retained in both scenarios. PR Close #41108 |
||
---|---|---|
.. | ||
animation_world | ||
core_all | ||
cyclic_import | ||
forms_reactive | ||
forms_template_driven | ||
hello_world | ||
hello_world_i18n | ||
hello_world_r2 | ||
injection | ||
router | ||
todo | ||
todo_i18n | ||
todo_r2 | ||
util | ||
README.md |
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 commands:
yarn bazel run --config=ivy //packages/core/test/bundling/injection:symbol_test.accept
yarn bazel run --config=ivy //packages/core/test/bundling/cyclic_import:symbol_test.accept
yarn bazel run --config=ivy //packages/core/test/bundling/forms:symbol_test.accept
yarn bazel run --config=ivy //packages/core/test/bundling/hello_world:symbol_test.accept
yarn bazel run --config=ivy //packages/core/test/bundling/router:symbol_test.accept
yarn bazel run --config=ivy //packages/core/test/bundling/todo:symbol_test.accept
Running all symbol tests
To run all symbol tests with one command, you can use the following scripts:
yarn run symbol-extractor:check
yarn run symbol-extractor:update