Skip to content

Node.js

Node.js runs JavaScript applications, builds and project tools. Choose an available branch according to application requirements.

Available versions

The catalog offers branches 22, 24 and 26. Installation resolves the newest available release in the selected branch for the supported architecture. This form does not accept an arbitrary patch version.

These options come from the application installation catalog. A catalog entry alone does not guarantee package availability on every server; verify the exact installed version in the service inventory.

Install and verify

  1. Select Node.js and the required branch.
  2. If the form offers a default-version option, assess its impact on other projects.
  3. Check the inventory and run the command shown on the service card as the project user after installation.
  4. Prepare matching npm if the project uses it.

Node.js is a runtime, not an automatically started application service. An available binary does not mean your application is running.

Terminal commands

Managed versions are separate from system packages. For example, Node.js 24 runs as /opt/grape-cloud/runtimes/node24/current/bin/node --version. The inventory identifier node24 is not a shell command. A green indicator confirms the installed runtime and its verification; it does not confirm that the shell can find the short node command through PATH.

Use Set as the terminal default on an installed service to verify the executables and create commands in /usr/local/bin. Node.js and npm switch together to the same Node.js branch. A separately installed managed npm for that branch takes precedence over bundled npm. This choice applies to the whole server. Unmanaged executable files are preserved. The user's PATH must include /usr/local/bin.

To use branch 24 only in the current terminal:

export PATH="/opt/grape-cloud/runtimes/npm24/current/managed-bin:/opt/grape-cloud/runtimes/node24/current/bin:$PATH"
node --version
npm --version

This example assumes both node24 and npm24 are installed. Activating default commands does not reinstall or download another runtime version.

Web application

Configure the startup command as a project process, including directory, user and environment. Use a web server reverse proxy pointing to the address and port where the application actually listens.

Configure builds and dependency installation in deployment. The command depends on your project's scripts.

Security updates

For fixed versions, runtime checks and update instructions, see Node.js: October 2026 security fixes.

Troubleshoot

If manual and process execution differ, check version, binary path, user and variables. Verify all dependent applications before switching the default branch.