Node.js Versions

The platform allows you to choose from the latest major NodeJS application server versions, as well as their associated process and package management tools.
Presently, the platform supports the following versions of this stack:

• 16.20.2
• 18.20.2
• 20.13.1
• 21.7.3
• 22.1.0

When setting up a new environment, you can specify the required Node.js version, and it’s also possible to change the Node.js version for an existing environment.

Create Node.js Environment

Step 1.  To get started, click the New Environment button at the top of the dashboard to launch the topology wizard.

Step 2. Switch to the Node.js tab and select the desired server version from the drop-down menu in the center of the screen.

Step 3. Choose your preferred process manager  (forever, npm, or pm2) from the drop-down list (highlighted in the image below):

A Node.js process manager is essential for managing your application’s lifecycle. It simplifies starting, stopping, and restarting processes on a node and can be set to automatically re-run scripts if the application fails to start or when the code is updated.

• npm: Manages additional application modules and packages using the package.json configuration file.
• forever: Keeps services running continuously by managing node processes (start, stop, restart).
• pm2: Offers advanced options such as monitoring, load balancing, and deployment, for more effective application management.

Finally, specify the remaining server and environment settings, environment name, etc.), and click the Create button at the bottom right corner of the screen.

Change Node.js Version

You can change the version of your Node.js server and process manager for an existing environment by following these steps:

Step 1. Open the redeploy container(s) dialog by either:

Clicking on the Change Environment Topology button next to the relevant environment.

In the open frame, click on the pencil icon next to the field where you want to edit your Node.js server version or tag.

Selecting the Redeploy Container(s) button next to the required node, or the appropriate environment layer to update all containers simultaneously.

Step 2. In the Redeploy container(s) dialog, configure the following options:

• Tag: Choose the desired Node.js version and preferred process manager.
• Keep volumes data: Ensure data in volumes is saved.
• Simultaneous or Sequential deployment with delay (for scaled servers only): Decide whether to redeploy all containers in a layer at once or one by one to minimize downtime.

Step 3. Click Redeploy and confirm your action in the pop-up dialog to complete the Node.js version update.