Skip to content

chore(deps-dev): bump @types/node #41

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.

Sign up for GitHub

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

Merged
steipete merged 1 commit into from
May 17, 2026
Merged

chore(deps-dev): bump @types/node #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"zod": "^4.4.3"
},
"devDependencies": {
"@types/node": "^24.10.1",
"@types/node": "^25.8.0",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align Node type definitions with supported runtime

Pinning @types/node to major 25 while the package still advertises "node": ">=22" allows TypeScript to accept Node 25-only APIs during development, which can then fail at runtime for users on Node 22–24. This creates a compatibility gap between compile-time checks and the documented support matrix, so the types major should track the minimum supported Node line (or runtime support should be raised to match).

Useful? React with 👍 / 👎.

"oxfmt": "^0.50.0",
"oxlint": "^1.64.0",
"typescript": "^6.0.3",
Expand Down
36 changes: 18 additions & 18 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading