Supported Node.js Versions

Warning: Support for Node.js version 18 is discontinued for Launch as of August 1, 2025. Update to a supported Node.js version to avoid disruptions in your projects.

The following are the available Node.js versions on Launch:

• 22.x (default)
• 20.x
• 18.x (discontinued as of August 1, 2025)

Setting the Node.js Version in the package.json File

You can specify the major Node.js version in the engines section of the package.json file.

Example:

package.json

{
  "engines": {
    "node": "20.x"
  }
}

When a valid semver range for Node.js 20 (e.g. 20.x) is specified in the package.json, the project will be deployed with the latest available 20.x version of Node.js.

Note: If the engines section is not specified in package.json, the default Node.js version (Node.js 22.x) will be used.

Example Version Ranges and their Deployed Node.js Versions:

Troubleshooting

If you encounter the following error when redeploying an existing project, it is likely due to the Node.js version settings:

ERROR: Node.js v18. is no longer supported on Launch. Please upgrade to a supported version to continue deploying your projects. View supported versions here: https://www.contentstack.com/docs/developers/launch/supported-nodejs-versions

Your latest live deployment was created before August 1, and your package.json does not specify an "engines" property. In such cases, the deployment still defaults to Node.js 18, which has now been discontinued. As a result, redeployments of these projects fail.

To ensure smooth deployments, explicitly define the Node.js version in your package.json:

1. Add the following snippet.
2. Commit the change.
3. Redeploy.

{
  "engines": {
    "node": "22.x"
  }
}

This configuration instructs the deployment system to use Node.js 22, which is the currently supported default version.

• Existing deployments (before August 1): Require an "engines" field update, otherwise redeployments will fail due to Node.js 18.
• New environments created after August 1: Default to Node.js 22 if no "engines" property is specified.
• New deployments on environments created before August 1: Will continue to use the previously set Node.js version (e.g., Node.js 18) unless explicitly updated via the "engines" field.