Node.js Versions

Node.js Versions

The platform lets you pre-select a current Node.js application-server release together with the required process and package managers. You can choose these options during environment creation or switch them later through container redeployment.

In this article

Available Node.js Versions

Node.js 1616.20.0
Node.js 2020.20.2
Node.js 2222.23.1
Node.js 2424.18.0
Node.js 2525.9.0
Node.js 2626.4.0
i

Versions are updated regularly

Check the weekly updated Software Stack Versions document before creating or redeploying a production environment.

Create a Node.js Environment

1

Open the topology wizard

Click New Environment at the top of the dashboard.

Create a new environment
Open the topology wizard from the dashboard.
2

Select the Node.js version

Open the Node.js programming-language tab and choose the required engine version from the central drop-down list.

Select a Node.js version
Choose the required Node.js release in the topology wizard.
3

Select the process manager

Use the tags drop-down list to choose npm, forever, or pm2.

Select a Node.js process manager
Choose npm, forever, or PM2 as the process manager.
npmManages application modules and packages through package.json.
foreverStarts, stops, and restarts processes and keeps services running continuously.
pm2Provides monitoring, load balancing, deployment, and advanced process-management options.
4

Complete the environment settings

Configure Cloudlet limits, region, environment name, and other required parameters, then click Create.

Change the Node.js Version

You can change the Node.js release and process manager for an existing environment through either the topology wizard or the direct redeploy action.

Option 1: Change Environment Topology

Click Change Environment Topology, then use the pencil icon to edit the Node.js version or tag.

Change Node.js environment topology
Open the topology editor for the environment.
Edit the Node.js version in the topology wizard
Edit the Node.js version or process-manager tag.

Option 2: Redeploy Containers

Click Redeploy Container(s) beside the required node or the complete Node.js layer.

Redeploy Node.js containers
Open the redeployment dialog for a node or layer.
  • Tag: Select the required Node.js version and process manager.
  • Keep volumes data: Preserve data stored in container volumes.
  • Simultaneous or Sequential deployment with delay: For scaled servers, choose whether all containers are redeployed together or one by one.
Node.js redeployment dialog
Choose the Node.js tag, volume preservation, and deployment strategy.

Click Redeploy and confirm the operation.

Confirm Node.js redeployment
Confirm the Node.js version change.

Expected Result

A new environment is created with the selected Node.js release and process manager, or an existing Node.js layer is redeployed to the selected version and tag.

Important Notes

  • Check Software Stack Versions before changing a production environment.
  • Back up application data and configuration before redeployment.
  • Use Keep volumes data when persistent volume content must be preserved.
  • Use sequential redeployment for a scaled layer when reducing downtime is important.
  • Confirm that the application and dependencies support the selected Node.js version.
  • Review application and process-manager logs after redeployment.