Skip to content

chore(deps-dev): bump @types/node from 20.19.41 to 25.9.0 #59

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
Moeabdelaziz007 merged 1 commit into from
May 18, 2026
Merged

chore(deps-dev): bump @types/node from 20.19.41 to 25.9.0 #59

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
16 changes: 8 additions & 8 deletions package-lock.json
View file
Open in desktop

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

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 @@ -68,7 +68,7 @@
},
"devDependencies": {
"@secretlint/secretlint-rule-preset-recommend": "^12.2.0",
"@types/node": "^20",
"@types/node": "^25",
Comment thread
greptile-apps[bot] marked this conversation as resolved.
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

What is the recommended @types/nodeversion for Node.js 22? Does@types/node version 25 exist and what Node.js version does it target?

💡 Result:

The recommended version of @types/node for Node.js 22 is the latest 22.x release [1][2][3]. The @types/node package follows a versioning convention where the major version of the package corresponds to the major version of Node.js it targets [4]. Yes, @types/node version 25 exists [1][2][3]. It targets Node.js 25 [1][2][3]. As of May 2026, the latest available version is 25.7.0 [2][3][5]. Because @types/node versions are aligned with Node.js major versions, you should install the version that matches your specific Node.js runtime major version to ensure accurate type definitions for the APIs available in your environment [4]. For example, if you are using Node.js 22, you should use @types/node@22.x [1][2][3].

Citations:

🏁 Script executed:

#!/bin/bash
# Check if there are any TypeScript compilation errors with the new types
if command -v npm &> /dev/null; then
  npm list `@types/node` 2>/dev/null || echo "`@types/node` not yet installed"
  
  # Check what Node.js version is specified and compare with types version
  echo "=== Engines requirement ==="
  cat package.json | jq -r '.engines.node // "not specified"'
  
  echo "=== `@types/node` version ==="
  cat package.json | jq -r '.devDependencies["`@types/node`"] // "not found"'
fi

Repository: AIX-Format/PiWorker-OS

Length of output: 213

Align @types/node version with minimum Node.js requirement.

The @types/node version v25 should be v22 or higher. @types/node versions correspond to Node.js major versions—v25 provides type definitions for Node.js 25, but your project requires Node.js >=22. Using v25 allows code to compile with APIs that may not exist in Node.js 22, 23, or 24, causing runtime failures. Update to @types/node@22 (or higher within your supported range) to match your minimum Node.js version.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 71, Update the devDependency for "`@types/node`" in
package.json to align with your minimum supported Node.js version by replacing
the current "^25" with a version compatible with Node.js >=22 (for example "^22"
or a specific 22.x release); after changing the version, regenerate the lockfile
and install dependencies (npm/yarn/pnpm install) so the lockfile and
node_modules reflect the new `@types/node` version and prevent using typings for
newer Node.js APIs.

"husky": "^9.1.7",
"lint-staged": "^16.4.0",
"prettier": "^3.8.3",
Expand Down
Loading