ERR_PNPM_BAD_PM_VERSION

[stiff chasm]

I am receving the following message below when deploying to vercel. How can I fix it?

[09:30:02.721]  ERR_PNPM_BAD_PM_VERSION  This project is configured to use v9.1.0 of pnpm. Your current pnpm is v9.0.4
[09:30:02.722] 
[09:30:02.722] If you want to bypass this version check, you can set the "package-manager-strict" configuration to "false" or set the "COREPACK_ENABLE_STRICT" environment variable to "0"
[09:30:02.737] Error: Command "pnpm install" exited with 1
[09:30:02.965] 

Locally

pnpm -v
9.1.0

[past echo]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[vernal ice]

the pnpm version on vercel is 9.0.4, which is not compatible with the version set in your package.json

[stiff chasm]

ok thanks

[past echo]

✅ Success!

This question has been marked as answered! If you have any other questions, feel free to create another post

Jump to answer

[Click here](#1241020698642743306 message)

[rigid shale]

How would you recommend using corepack with vercel? I have packageManager specified in package.json. It conains a specific version of pnpm which is upgraded by Renovate just as any other dependency. Since recently vercel builds fail for this PR: https://github.com/kachkaev/njt/pull/672. Similar PRs used to work in the past — vercel respected packageManager directive: https://github.com/kachkaev/njt/pulls?q=is%3Apr+is%3Aclosed+pnpm

Vercel build logs:

ERR_PNPM_BAD_PM_VERSION  This project is configured to use v9.1.2 of pnpm. Your current pnpm is v9.0.4

[vernal ice]

appears to be a vercel bug: https://github.com/vercel/vercel/issues/11607

[rigid shale]

Thanks for the link! I was able to bypass this error by setting ENABLE_EXPERIMENTAL_COREPACK=1 in the list of env vars (via Vercel UI).