Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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 apps/homework/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
},
"devDependencies": {
"@types/react": "^18.2.0",
"@types/node": "^20.4.2",
"@types/node": "^25.3.2",
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

CI uses Node.js v20, but this updates @types/node to v25. If the runtime is still Node 20, consider pinning @types/node to the matching major to avoid typings advertising newer Node APIs than are actually available at runtime (or update runtime/CI/engines accordingly).

Suggested change
"@types/node": "^25.3.2",
"@types/node": "^20.0.0",

Copilot uses AI. Check for mistakes.
"typescript": "^5.1.6"
}
}
2 changes: 1 addition & 1 deletion apps/roadbook/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
},
"devDependencies": {
"@types/react": "^18.2.0",
"@types/node": "^20.4.2",
"@types/node": "^25.3.2",
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

The repo CI workflow pins Node.js to v20, but this bumps the TypeScript Node typings to v25. That can make it easy to accidentally use APIs that don’t exist on the runtime the project actually runs/tests on. Consider keeping @types/node aligned to the supported Node major (or update the runtime/CI/engines to match).

Suggested change
"@types/node": "^25.3.2",
"@types/node": "^20.0.0",

Copilot uses AI. Check for mistakes.
"typescript": "^5.1.6",
"@next/mdx": "13.4.12",
"@mdx-js/loader": "^2.3.0"
Expand Down
Loading
Loading