pnpm 11 and 12 not supported

Author: thernstigCreated Aug 12, 2026Updated Sep 17, 2026

https://vercel.com/docs/package-managers does not list pnpm 11, which was released almost 4 months ago,

Note that pnpm 12.0 is significantly faster, so it should be prioritized to fix this now.

vercel fails when using it:

bash

> vercel
Vercel CLI 58.9.1 (Node.js 24.19.0)
  Inspect         <redacted>
  Preview         <redacted>
2026-08-12T07:33:06.099Z  Running build in Washington, D.C., USA (East) – iad1
2026-08-12T07:33:06.099Z  Build machine configuration: 4 cores, 8 GB
2026-08-12T07:33:06.137Z  Retrieving list of deployment files...
2026-08-12T07:33:06.456Z  Downloading 226 deployment files...
2026-08-12T07:33:07.771Z  Restored build cache from previous deployment (6cxCXfEBPZEB3noz9YP1cZYJFzJm)
2026-08-12T07:33:08.112Z  Running "vercel build"
2026-08-12T07:33:08.126Z  Vercel CLI 58.1.0
2026-08-12T07:33:08.399Z  Error while parsing config file: "/vercel/path0/pnpm-lock.yaml"
2026-08-12T07:33:08.439Z  Error while parsing config file: "/vercel/path0/pnpm-lock.yaml"
2026-08-12T07:33:08.440Z  Installing dependencies...
2026-08-12T07:33:08.934Z  npm error code EBADDEVENGINES
2026-08-12T07:33:08.935Z  npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
2026-08-12T07:33:08.935Z  npm error EBADDEVENGINES Invalid devEngines.packageManager
2026-08-12T07:33:08.935Z  npm error EBADDEVENGINES Invalid name "pnpm" does not match "npm" for "packageManager"
2026-08-12T07:33:08.936Z  npm error EBADDEVENGINES {
2026-08-12T07:33:08.936Z  npm error EBADDEVENGINES   current: { name: 'npm', version: '11.12.1' },
2026-08-12T07:33:08.936Z  npm error EBADDEVENGINES   required: { name: 'pnpm', version: '^11.0.0', onFail: 'error' }
2026-08-12T07:33:08.936Z  npm error EBADDEVENGINES }
2026-08-12T07:33:08.937Z  npm error A complete log of this run can be found in: /vercel/.npm/_logs/2026-08-12T07_33_08_543Z-debug-0.log
2026-08-12T07:33:08.972Z  Error: Command "npm install" exited with 1

Also https://vercel.com/docs/package-managers does not mention the more modern, proper usage of devEngines.packageManager which is preferred over the old packageManager.

json

  "devEngines": {
    "packageManager": {
      "name": "pnpm",
      "version": "^11.0.0",
      "onFail": "error"
    }
  },

https://vercel.com/docs/builds/configure-a-build#install-command and probably many other packages mentions the old packageManager and should be updated to include devEngines.packageManager.

Good to know that pnpm 12 will soon be released and everyone will want to upgrade to that as well, as it contains huge performance boosts. Also, Corepack is not a good solution as it is being removed from Node.js 26. Many users depend on other solutions.

It seems there is no way to deploy if you have upgraded to pnpm 11

Source: vercel/vercel

View original on GitHub View discussion on GitHub