chore(deps): update typescript to v6#2514
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
joshuaellis
force-pushed
the
chore/typescript-v6
branch
from
85360fe to
97509d4
Compare
joshuaellis
force-pushed
the
chore/typescript-v6
branch
from
97509d4 to
b60c25f
Compare
joshuaellis
force-pushed
the
chore/typescript-v6
branch
from
b60c25f to
81521d6
Compare
Bumps root devDependencies.typescript from 5.7.2 → 6.0.3, and the publish-ci consumer fixtures (cra5, next, vite) from 4.9.5 → 6.0.3. Stacked on the tsdown migration: tsup's deprecated baseUrl injection is gone, so TS 6 (which hard-errors on baseUrl) compiles cleanly with no tsconfig workaround in any job. The test-types matrix '6.0' entry now takes the same path as the rest of the matrix. Closes #2491.
joshuaellis
force-pushed
the
chore/typescript-v6
branch
from
81521d6 to
0b99f62
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Take the TypeScript 6 upgrade — the blocker on #2491 is gone now that the bundler swap landed. With
tsup'sbaseUrlinjection out of the picture, TS 6 (which hard-errors onbaseUrlvia TS5101) compiles cleanly with notsconfigworkaround in any job, and thetest-typesmatrix'6.0'entry takes the same path as the rest of the matrix.The vite and next publish-ci fixtures move forward with the same bump — their tsconfigs were written against TS 4.x defaults that TS 6 deprecates, and modernising them to
moduleResolution: "bundler"(plusesModuleInterop: truein vite) is closer to what a real Vite/Next consumer would do. The cra5 fixture stays on TS 4.9.5 becausereact-scripts@5.0.1declarespeerOptional typescript@"^3.2.1 || ^4"and can't accept TS 6 without--legacy-peer-deps; CRA is EOL and that fixture's value is precisely "older CRA consumer still works".Closes #2491.