-
Notifications
You must be signed in to change notification settings - Fork 0
chore: add @types/node dependency to multiple packages #180
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -70,6 +70,7 @@ | |||||
| "@eslint/js": "9.39.2", | ||||||
| "@rsbuild/core": "1.7.5", | ||||||
| "@rslib/core": "0.20.2", | ||||||
| "@types/node": "25.5.0", | ||||||
|
||||||
| "@types/node": "25.5.0", | |
| "@types/node": "^21.1.0", |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
This package declares
engines.nodeas ">=21.1.0" (see bottom of this file), but the added@types/nodeis pinned to25.5.0. That mismatch can let TypeScript typecheck Node 25-only APIs even though the package claims compatibility with Node 21+, which can lead to runtime incompatibilities. Consider either aligning@types/nodeto the minimum supported Node major (or a compatible range), or bumping theengines.noderequirement to match the typings being used.