angular/packages/localize/tools
Paul Gschwendtner a3908bd0fc build: enable code splitting for esbuild bundling of localize tools (#43932)
Enables code spitting for ESBuild bundling of the localize/tools entry
point. When we initially configured ESBuild as part of APF v13, we left
this option disabled as code splitting is marked experimental. The ESM
splitting mechanism in ESBuild seems very solid so far (judging subjectively
and by experience/reports in the ESBuild repo), so we should give it a shot,
in order to significantly reduce the size of the NPM package, and simplify
debugging (by not having duplicated code portions for all the different entry points).

To clarify: Code splitting is helpful as we have multiple entry-points
that currently duplicate code. With code splitting these entry-points
would share common code instead.

PR Close #43932
2021-10-26 23:58:27 +00:00
..
src feat(localize): support "associated message ids" for placeholders (#43534) 2021-10-18 09:23:59 -07:00
test feat(localize): support "associated message ids" for placeholders (#43534) 2021-10-18 09:23:59 -07:00
BUILD.bazel build: enable code splitting for esbuild bundling of localize tools (#43932) 2021-10-26 23:58:27 +00:00
esbuild.config.js refactor: expose new @angular/localize/tools entry-point for CLI usage (#43431) 2021-10-01 18:28:44 +00:00
index.ts refactor: expose new @angular/localize/tools entry-point for CLI usage (#43431) 2021-10-01 18:28:44 +00:00
README.md refactor: expose new @angular/localize/tools entry-point for CLI usage (#43431) 2021-10-01 18:28:44 +00:00

Disclaimer

The localize tools are consumed via the Angular CLI. The programmatic APIs are not considered officially supported though and are not subject to the breaking change guarantees of SemVer.