Vercel@41.4.0 throw error "ERR_PNPM_LOCKFILE_CONFIG_MISMATCH"

Feedback
1

Summary: When deploying with vercel cli version 41.4.0, ERR_PNPM_LOCKFILE_CONFIG_MISMATCH error occurs when pnpm install --frozen-lockfile command is executed.

  • No changes were made to the pnpm-lockfile file.
  • When I printed out the pnpmfileChecksum in the vercel build environment, it matched the pnpmfileChecksum in pnpm-lock.yaml in the github repository.
  • pnpm version: 9.15.9, vercel version: 41.4.0

For internal project reasons, we are deploying with vercel cli in github action workflow

I modified the code so that I don’t get the ‘ERR_PNPM_LOCKFILE_CONFIG_MISMATCH’ error when triggered automatically to vercel, but when deploying with vercel cli, I get the error.

I was installing vercel cli with the command npm i -g vercel, and since version 41.4.0 was recently released, I deployed to the version below it, 41.3.2, and it worked fine.

1 Like
2

This can happen if your local PNPM version is different than what Vercel uses by default. You should be able to solve it by configuring a specific version. You can learn more about that here: Configuring a Build

1 Like
3

Thank you for your response! :slight_smile:

I guess I wasn’t very clear in my explanation.
The package.json already had the packageManager set to “pnpm@9.10.0”.

But when I printed pnpm --version in vercel build environment, it came out as 9.15.9. So I changed pnpm to 9.15.9 locally and tried to install pnpm, and it installed normally without ERR_PNPM_LOCKFILE_CONFIG_MISMATCH error.

1 Like