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 .nvmrc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v20.19.2
20.19.6
2 changes: 1 addition & 1 deletion .tool-versions
Original file line number Diff line number Diff line change
@@ -1 +1 @@
nodejs 20.19.2
nodejs 20.19.6
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "roo-code",
"packageManager": "pnpm@10.8.1",
"engines": {
"node": "20.19.2"
"node": "20.19.6"
},
"scripts": {
"preinstall": "node scripts/bootstrap.mjs",
Expand Down
2 changes: 1 addition & 1 deletion src/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
},
"engines": {
"vscode": "^1.84.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

[P2] Avoid duplicating engines.node across root and src/package.json. VS Code extensions run on the extension host's Node bundled with VS Code; pinning engines.node here can block installs unnecessarily. Consider removing engines.node from src/package.json and rely on the root engines plus .nvmrc/.tool-versions for dev/CI pinning.

"node": "20.19.2"
"node": "20.19.6"
},
"author": {
"name": "Roo Code"
Expand Down
Loading