VERCEL ERRORS

Node.js version mismatch on Vercel

Your local Node.js version and the version Vercel builds with can differ. Set the version in the project settings or in package.json engines, then verify it.

What it means

A new Vercel project uses the latest Node.js LTS version available on Vercel. Only major versions are offered, and Vercel rolls out minor and patch updates itself. At the time this page was checked, the documentation listed 24.x (the default) and 22.x. Check the documentation for the current list.

A version set in the engines.node field of package.json overrides the version chosen in the project settings.

How to fix it

  1. Run node -v on your machine and note the major version you develop with.
  2. Find the version Vercel uses by running node -v in the Build Command, or by logging process.version.
  3. Choose the version under Settings, Build and Deployment, Node.js Version. It applies to new deployments.
  4. Or set engines.node in package.json, which overrides the project setting.
  5. Mind the range you write. The documentation shows that >=22.0.0 deploys the latest 24.x version, while 22.x and ^22.0.0 deploy 22.x.
{
  "engines": {
    "node": "24.x"
  }
}

What a DeployDoctor scan can check

The build configuration check reports an engines.node range that Vercel cannot run. A scan reads package.json from the repository. It cannot see the Node.js version saved in your Vercel project settings.

Sources

Documentation last checked 2026-10-28. Vercel can change its documentation; confirm against the linked pages.