Node.js
Install Node.js versions, choose the default, and keep npm up to date.
Node applications pin the version they want, and the server can hold several at
once. Node.js lists the versions OSS Panel manages, lets you add or remove
one, and decides which version the bare node command means.
The version card
Each card shows:
- The version, with Default if it is the one
noderesolves to. - A lifecycle badge — Current, Long-term support (with its codename), Maintenance only, or No longer supported — and the date support ends.
- The npm version it ships with, and an arrow to the newer one if there is a newer one.
- Which applications use it, or No applications use this version yet.
- Update npm, Make default and Remove.
The default only changes the node command
Exactly as with PHP: "Your applications keep their own version — this only
changes the node command." To move an application, change it on the
application's own screen.
Install a version
Click Install version. Only versions this server can install are listed; the panel reads the list from nodejs.org.
Pick the version and click Install. It takes a few minutes and reports Preparing → Downloading → Unpacking → Configuring on the new card. The page updates on its own.
A version past end of life carries the same warning PHP does — install it only if an application needs it.
If the list cannot be fetched, the dialog says so and tells you to check that the server can reach nodejs.org.
Updating npm
Update npm upgrades npm inside that Node version only. If it is already current the button explains itself rather than doing nothing silently — "npm is already the newest version."
Limits and caveats
- The panel manages versions installed through fnm. A Node the distribution installed independently is not listed; where the panel detects one it says so in a note under the cards: "This server also has Node.js 20 of its own. The panel doesn't manage it, so it isn't listed above."
- Removing a version removes what was installed for it — global packages included. You can install the version again, but not its globals.
- On a container server there is nothing to manage. The page says "This server hosts containers and runs no applications on the host itself… A container brings its own runtime."
- Process management for a Node application — the start command, restarts, workers — lives on the application's workers screen, not here.