Upgrade @types/node to the latest Node 24.x-line release - #1232
Draft
dgee2 wants to merge 1 commit into
Draft
Conversation
Bumps @types/node 25.6.0 -> 24.13.3. This looks like a downgrade by package version but isn't: @types/node versions track Node.js release lines 1:1, and 25.x/26.x type Node's non-LTS "Current" lines while this repo's engines.node only targets LTS lines (^20.19.0 || ^22.13.0 || >=24.0.0). Moving to the latest 24.x release aligns the types with an actual supported runtime instead of type-checking against APIs that may not exist on Node 20/22/24. Verified: lint, build (type-check + vite build), unit tests (57/57), storybook interaction tests (78/78). Co-authored-by: Claude <noreply@anthropic.com>
dgee2
force-pushed
the
deps-types-node-major
branch
from
August 13, 2026 21:45
2657d23 to
dbffd92
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.
Bumps @types/node 25.6.0 -> 24.13.3. This looks like a downgrade by
package version but isn't: @types/node versions track Node.js release
lines 1:1, and 25.x/26.x type Node's non-LTS "Current" lines while
this repo's engines.node only targets LTS lines
(^20.19.0 || ^22.13.0 || >=24.0.0). Moving to the latest 24.x release
aligns the types with an actual supported runtime instead of
type-checking against APIs that may not exist on Node 20/22/24.
Verified: lint, build (type-check + vite build), unit tests (57/57),
storybook interaction tests (78/78).
Co-authored-by: Claude noreply@anthropic.com
Stack created with GitHub Stacks CLI • Give Feedback 💬