Repository navigation
chore: upgrade types/node and typescript to v6 - #32
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Summary
@types/node20.5.0 -> 24.13.3 — the latest of the 24.x line, matching the Node version inmise.tomltypescript5.9.3 -> 6.0.3Batched because both touch only
package.json/pnpm-lock.yaml, and separate PRs would just conflict.Why not
@types/node26@types/nodemajors track Node majors. 26.x describes APIs that do not exist in Node 24, socode would type-check and then fail at runtime.
pnpm outdatedand dependabot will keepoffering it; the version is pinned exactly and the reasoning is now in the README so the trap
is visible rather than rediscovered.
TypeScript 6: no fallout, unlike
kahlstrm/webTypeScript 6 turns
stricton by default. Inwebthat surfaced two realts(7053)errors,because its tsconfig never set it. Here
strict: truehas been explicit since thecreate-next-appscaffold, so the new default changes nothing.@typescript-eslint/parser(used by the narrow ESLint pass) accepts TS 6 — lint is clean andpnpm peers checkreports no issues.TypeScript 7 is not included: it is the native port, and the ecosystem is still catching up.
Testing
pnpm test:unit— 18 passedpnpm test:e2e— 9 passedpnpm lint/pnpm format:check— cleanpnpm build— compilespnpm peers check— no issues