---
title: "Node.js v18 is no longer supported on Launch: fix Node version errors"
url: "https://developers.contentstack.com/guides/fix-failing-launch-builds/node-version-errors"
type: "guide_chapter"
level: "intermediate"
intent: "fix"
outcome: "Your Launch environments build on a Node version you chose in package.json, and you can confirm which version each deployment used."
prerequisites:
  - "A Launch environment that fails to redeploy, or one you want to move to a newer Node version"
  - "Write access to the repository's package.json"
next:
  - "https://developers.contentstack.com/guides/fix-failing-launch-builds/private-npm-packages-and-e401"
tags:
  - "headless"
  - "cli"
  - "next"
authors:
  - "Tim Benniks"
published: "2026-11-15T10:55:17.479Z"
updated: "2026-11-15T10:55:17.479Z"
---

# Node.js v18 is no longer supported on Launch: fix Node version errors

- **Authors:** Tim Benniks
- **Published:** 2026-11-15T10:55:17.479Z
- **Level:** Intermediate
- **Intent:** Fix
- **Tags:** headless, cli, next

---

You redeploy a site that has been running on Launch for a year, and the build stops before it starts. Nothing in your code changed. A new environment created from the same repository deploys fine. The difference is the Node.js version, and the fix is one field in package.json.

## What you'll learn

- Why older Launch environments fail with a Node 18 error


- Why existing environments don't move to a newer Node version on their own


- How to pin the version with engines.node


- How to confirm which Node version a deployment used



## Symptoms

- The deployment fails right away with:



```text
Node.js v18 and below are no longer supported on Launch.
```

- An environment that deployed fine before fails on redeploy, while a new environment or project from the same repository works.


- You updated your dependencies with npm update or pnpm update and the error is still there.


- After a platform update, a feature that depends on the runtime behaves differently, and you want to go back to the previous major version.



## Why it happens

Launch concept: Launch supports Node.js 20.x, 22.x and 24.x. You choose the major version with the engines.node field in package.json. Without it, a new environment uses the current default, Node.js 24.x.

Node.js 18 was discontinued on Launch on August 1, 2025. Before that, an environment without engines.node was created on Node 18. That choice sticks: an existing environment keeps the version it was configured or defaulted with, and Launch doesn't move it to a newer major version on its own. A jump from 18 to 22 or 24 can break native modules, crypto defaults or build tooling, so Launch stops the deployment and asks you to choose instead of upgrading silently.

That explains the confusing part. The old environment fails because it is still on Node 18. The new environment works because it was created after the default changed.

Updating packages doesn't help, because dependencies don't select the runtime. Only engines.node does.

## Fix it

### Pin engines.node

Add the engines field to the package.json at the root of what Launch builds:

```json
{
  "name": "my-site",
  "engines": {
    "node": "22.x"
  }
}
```

Use a major version range such as 20.x, 22.x or 24.x. Launch keeps that major version and applies the latest minor and patch releases for it, so a range is better than an exact version like 22.18.0.

Pick the version your app runs on locally. If you were on Node 18 and want the smallest jump, start with 20.x or 22.x and test there before moving to 24.

Commit, push, and let the environment redeploy, or trigger a deployment yourself. Every environment that builds from this branch picks up the same version.

### Test the upgrade before production

A major version change is a code change, so treat it like one:

- Switch your local Node version with nvm use 22 or your version manager of choice.


- Delete node_modules, reinstall and run a production build: npm ci && npm run build.


- Push the engines change to a branch that deploys to a preview or staging environment on Launch.


- Promote to production once that environment is healthy.



Watch for native dependencies such as image processing or headless browser packages. They are the most likely to need a new version for a newer Node major.

### Move back to a previous major version

The same field works in reverse. If a feature breaks after the default moved to a newer major version, pin the previous one, for example "node": "22.x", and redeploy while you investigate. An environment without engines.node can't be rolled back to a specific version any other way.

### If you can't change the code right now

A new environment without engines.node starts on the current default. Creating one from the same branch gets you onto a supported version without a commit, but you lose the old environment's variables and settings unless you copy them over. Treat it as a stopgap and add engines.node when you can.

## Check that it worked

Print the version at the start of the build. Set the build command in the environment settings to:

```bash
node -v && npm run build
```

The first line of the build step in the deployment log shows the version, for example v22.x.y. Read it from a terminal with:

```bash
csdx launch:logs --environment production --deployment <deployment-uid> --type d
```

For the runtime version on a live SSR site, log process.version once at server start and look for it in the server logs (--type s).

## Prevent it

- Set engines.node in every project you deploy to Launch, including old ones that work today. It makes builds reproducible and turns the next Node retirement into a one-line change you make on your schedule.


- Add an .nvmrc with the same major version so local development and Launch agree.


- Review the version once a year against the [supported Node.js versions](https://www.contentstack.com/docs/developers/launch/supported-nodejs-versions) and plan the upgrade before a version is retired.


- Redeploy long-running sites now and then. Monthly patch updates only reach a project when it is redeployed.



## Key takeaways

- Node.js v18 and below are no longer supported on Launch means the environment still runs Node 18. Set engines.node to 20.x, 22.x or 24.x.


- Existing environments keep their Node version. Only new environments get the current default, Node.js 24.x.


- npm update and pnpm update don't change the runtime. engines.node does.


- Use a major range like 22.x so you keep receiving patch updates.


- Put node -v in the build command when you need to prove which version ran.





---

## Do this with AI

Install the launch-platform skill from [Contentstack agent skills](https://github.com/contentstack/contentstack-agent-skills) and connect the Launch Deploy Helper profile in MCP Profile Hub. Then ask your agent:

> List the environments in my Launch project and, for each one, read the deployment log of its latest deployment and tell me which Node.js version it built with. Flag any environment that is still on Node 18 or has no engines.node in package.json.

New to this? [Set up your AI workbench](/guides/set-up-your-ai-workbench-for-contentstack) first.




---

## Frequently asked questions

### Which Node.js versions does Launch support?

Node.js 20.x, 22.x and 24.x. Node.js 18 was discontinued on Launch on August 1, 2025.

### What Node version does Launch use if I don't set engines.node?

New environments use the current default, Node.js 24.x. Existing environments keep the version they were first deployed with, which can be Node 18 for older ones.

### Does running npm update or pnpm update change the Node version on Launch?

No. Updating dependencies doesn't touch the runtime. Only the engines.node field in package.json selects the Node version.

### Will Launch apply Node security patches automatically?

Launch updates each supported major version to its latest minor and patch release once a month. A project picks up the update on its next deployment.



---

## Chapter Navigation

**← Previous:** [Launch env vars undefined or deploy stuck in Deploying](https://developers.contentstack.com/guides/fix-failing-launch-builds/env-vars-undefined-or-deploy-stuck)

**Next →:** [npm error code E401 on Launch: install private packages](https://developers.contentstack.com/guides/fix-failing-launch-builds/private-npm-packages-and-e401)
