Closed tanner-reits closed 2 weeks ago
@stencil/core@4.18.3 ts tsc --noEmit --project scripts/tsconfig.json && tsx scripts/tech-debt-burndown-report.ts
--strictNullChecks
error reportTypechecking with --strictNullChecks
resulted in 1080 errors on this branch.
That's the same number of errors on main, so at least we're not creating new ones!
There are 15 unused exports on this PR. That's the same number of errors on main, so at least we're not creating new ones!
Download the tarball here: https://github.com/ionic-team/stencil/actions/runs/9471194069/artifacts/1594214541
If your browser saves files to ~/Downloads
you can install it like so:
unzip -d ~/Downloads ~/Downloads/stencil-core-4.18.3-dev.1718203297.5cb4110.tgz.zip && npm install ~/Downloads/stencil-core-4.18.3-dev.1718203297.5cb4110.tgz
What is the current behavior?
Stencil does not generate export maps for any entry points.
GitHub Issue Number: N/A
What is the new behavior?
Stencil will generate export maps at build time. This include the default entry point, entry points for the lazy-loader (if applicable), and each custom element (if applicable).
This behavior is gated behind a new config flag.
Documentation
https://github.com/ionic-team/stencil-site/pull/1443
Does this introduce a breaking change?
Testing
Unit tests were added for the new behavior.
This feature can be manually tested by installing a build of this branch into the component starter and enabling the
generateExportMaps
config flag.Other information