-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(typescript): update to typescript 5.2 #4852
Conversation
|
Path | Location | Error | Message |
---|---|---|---|
src/dev-server/client/hmr-images.ts | (46, 46) | TS2345 |
reports and statistics
Our most error-prone files
Path | Error Count |
---|---|
src/dev-server/index.ts | 37 |
src/mock-doc/serialize-node.ts | 36 |
src/dev-server/server-process.ts | 32 |
src/compiler/build/build-stats.ts | 27 |
src/compiler/output-targets/dist-lazy/generate-lazy-module.ts | 25 |
src/compiler/style/test/optimize-css.spec.ts | 23 |
src/runtime/vdom/vdom-render.ts | 23 |
src/testing/puppeteer/puppeteer-element.ts | 23 |
src/compiler/prerender/prerender-main.ts | 22 |
src/runtime/client-hydrate.ts | 19 |
src/screenshot/connector-base.ts | 19 |
src/compiler/config/test/validate-paths.spec.ts | 16 |
src/dev-server/request-handler.ts | 15 |
src/compiler/prerender/prerender-optimize.ts | 14 |
src/compiler/sys/stencil-sys.ts | 14 |
src/compiler/transpile/transpile-module.ts | 14 |
src/runtime/vdom/vdom-annotations.ts | 14 |
src/sys/node/node-sys.ts | 14 |
src/compiler/build/build-finish.ts | 13 |
src/compiler/prerender/prerender-queue.ts | 13 |
Our most common errors
Typescript Error Code | Count |
---|---|
TS2345 | 436 |
TS2322 | 413 |
TS18048 | 321 |
TS18047 | 99 |
TS2722 | 38 |
TS2532 | 36 |
TS2531 | 25 |
TS2454 | 15 |
TS2352 | 13 |
TS2769 | 10 |
TS2790 | 10 |
TS2538 | 8 |
TS2344 | 5 |
TS2416 | 4 |
TS2493 | 3 |
TS18046 | 2 |
TS2684 | 1 |
TS2488 | 1 |
TS2464 | 1 |
TS2430 | 1 |
Unused exports report
There are 12 unused exports on this PR. That's the same number of errors on main, so at least we're not creating new ones!
Unused exports
File | Line | Identifier |
---|---|---|
src/runtime/bootstrap-lazy.ts | 21 | setNonce |
src/screenshot/screenshot-fs.ts | 18 | readScreenshotData |
src/testing/testing-utils.ts | 198 | withSilentWarn |
src/utils/index.ts | 140 | CUSTOM |
src/compiler/app-core/app-data.ts | 25 | BUILD |
src/compiler/app-core/app-data.ts | 114 | Env |
src/compiler/app-core/app-data.ts | 116 | NAMESPACE |
src/compiler/fs-watch/fs-watch-rebuild.ts | 110 | updateCacheFromRebuild |
src/compiler/types/validate-primary-package-output-target.ts | 62 | satisfies |
src/compiler/types/validate-primary-package-output-target.ts | 62 | Record |
src/testing/puppeteer/puppeteer-declarations.ts | 485 | WaitForEventOptions |
src/compiler/sys/fetch/write-fetch-success.ts | 7 | writeFetchSuccessSync |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a quick pass through - can you do me a favor and make sure this is marked as a feat()
please?
d8ee609
to
9af43f3
Compare
@alicewriteswrongs can you open a PR to update the Doc Site's table for TS support? |
oops forgot to copy-paste it! it's up already: stenciljs/site#1238 |
This upgrades us to TypeScript 5.2.2. The only change we had to make was to adjust the `module` setting in `scripts/package.json` in order to account for this change: https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#module-and-moduleresolution-must-match-under-recent-node-js-settings
9af43f3
to
d3aa1f8
Compare
This adds an entry to the table where we note the versions of Stencil where we upgrade TypeScript to include information about the forthcoming upgrade to TypeScript 5.2.2 in Stencil 4.4.0. See also stenciljs/core#4852
This adds an entry to the table where we note the versions of Stencil where we upgrade TypeScript to include information about the forthcoming upgrade to TypeScript 5.2.2 in Stencil 4.4.0. See also stenciljs/core#4852
This does the TS 5.2 upgrade. In order to get the project to build I didn't have to do much other than install the package.
I did have to adjust the
module
setting inscripts/package.json
, to account for this change: https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#module-and-moduleresolution-must-match-under-recent-node-js-settingsWhat is the current behavior?
Yucky, old, awful typescript 5.1!
What is the new behavior?
TypeScript 5.2
Does this introduce a breaking change?
Testing
After upgrading the package I built it locally and installed it into Framework and checked that Framework builds with no issues and the tests run.
Other information