Closed tanner-reits closed 2 weeks ago
Download the tarball here: https://github.com/ionic-team/stencil/actions/runs/9487277437/artifacts/1594945266
If your browser saves files to ~/Downloads
you can install it like so:
unzip -d ~/Downloads ~/Downloads/stencil-core-4.18.3-dev.1718214344.a39a6b2.tgz.zip && npm install ~/Downloads/stencil-core-4.18.3-dev.1718214344.a39a6b2.tgz
@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!
What is the current behavior?
There is a discrepancy between how Stencil handles errors in synchronous vs asynchronous component lifecycle methods. In synchronous components, the error is thrown, but the component will still render. For async, the error block component rendering.
Fixes: #5824
What is the new behavior?
The runtime will now catch errors thrown from async lifecycle methods, log them, and then continue the render cycle.
Documentation
Does this introduce a breaking change?
Testing
Validated fix in the associated issue's reproduction case.
Other information