Node.js comes ready in every environment: node, npm, npx and corepack work in the terminal, in your agents' commands and in npm scripts. Several Node.js versions can be installed side by side, and each project uses the one it asks for.
Which version a project gets
node, npm, npx and corepack pick the version in this order:
- the project's
.nvmrcor.node-versionfile (looked up from the folder you are in to the project's root in~/Code), such as22,v22.11.0,lts/*ornode; - the version chosen for the project on the panel or with
rdev node use; - the default version.
A file that asks for a version that is not installed stops with a message telling you to install it; rdev does not install it on its own. Version ranges such as ^20 are not understood; write the major version instead.
On the panel
Open the server from Servers in the sidebar, then Runtime. The Node.js card lists the installed versions with their exact release and which projects are pinned to each. Add Node.js version installs another one (the current release and the maintained LTS lines: 26, 24 and 22 today); the newest release of that version is downloaded from nodejs.org and checked against its published checksums. The ⋯ menu on a version makes it the default or removes it; the default and a version a project is pinned to cannot be removed. Under Projects, the pencil next to a project pins it to a version or sends it back to the default. This needs rdev 0.2.0-beta.35 or later.
On the server
rdev node list # installed and available versions, the default and the pinned projects
rdev node install 22 # the newest Node 22
rdev node default 22
rdev node use shop 22 # pin a project; rdev node use shop default undoes it
rdev node remove 24
rdev node update # the newest release of every installed version
Agents use the same commands, and over MCP rdev_node_list, rdev_node_install and rdev_node_project. While a subscription needs attention, installing, removing and switching versions are paused like PHP's.
Global packages
npm install -g works without sudo, and global packages are shared by every Node.js version, so a CLI you install once stays on the PATH whichever version a project uses. A package with a native addon is built for the version that installed it; reinstall it after switching if it complains. Packages installed globally before rdev 0.2.0-beta.35 stay with the version that was there then; install them again once.