VERCEL ERRORS

ERR_PNPM_UNSUPPORTED_ENGINE on Vercel

The pnpm version on Vercel does not match engines.pnpm in package.json. Pin pnpm with Corepack or remove the engines.pnpm value.

ERR_PNPM_UNSUPPORTED_ENGINE

What it means

Vercel documents this error as occurring when package.json#engines.pnpm does not match the version of pnpm that is running. The engine-strict setting cannot solve it, because engine-strict only handles dependencies.

How to fix it

  1. Either set the environment variable ENABLE_EXPERIMENTAL_COREPACK to 1 in the Vercel project and set packageManager in package.json to the pnpm version you want.
  2. Or remove the engines.pnpm value from package.json.
  3. Corepack is described by Vercel as experimental, so breaking changes or removal may occur in a future Node.js release.
{
  "engines": {
    "pnpm": "^7.5.1"
  },
  "packageManager": "pnpm@7.5.1"
}

What a DeployDoctor scan can check

The checks DeployDoctor documents do not include engines.pnpm. A scan can report a lockfile that is out of step with package.json and more than one lockfile in the repository, which are separate install problems.

Sources

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