Pnpm install fails with shared-workspace-lockfile=false

[lukasgerm]

Hey peoples,

I have a repository and I am trying to deploy it to vercel

I tried deploying it, it worked. But now if I push a commit and let it redeploy, it fails on the pnpm install step:

Lockfile is up to date, resolution step is skipped
Already up to date
undefined
/vercel/path0/packages/test-package:
ENOENT ENOENT: no such file or directory, open '/vercel/.local/share/pnpm/store/v3/files/f3/83154a33041cff854113f2de95fdb13555fc83487b1ef5b3d4cbd869b9146fd61b54aa5de2b267493bfdb958ff815d3b3235d82072d6f19ce2883f7aeb347f-index.json'

Error: Command "pnpm install" exited with 254

I am pretty sure its related to the shared-workspace-lockfile=false

No specific configuration. Just plain standard.

Here is the project.

GitHub - LukasGerm/pnpm-next-test: Showcase of the module resolution errors

[pawlean (Pauline P. Narvas)]

Hi, Lukas!

Thank you for your patience

Here’s a post that may be helpful to the 404 error that you’re seeing. Could you go through it and let us know what works?

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

[pawlean (Pauline P. Narvas)]

Cross-posting this answer as well in case it’s helpful.

Vercel Deploy error due to pnpm 10.4

Hello! It sounds like your project is using pnpm@10 in Vercel CI while you are using pnpm@9 locally? If so, this problem is not actually caused by pnpm@10. This will also happen with pnpm@9 in Vercel CI due to pnpm’s frozen lockfile feature which is enabled in CI environments. To fix this error, update your lockfile with pnpm i. If you want to match your local environment and use pnpm@9 instead of pnpm@10 for this project, you can enable Corepack. Hope this helps, and happy to answer any fol…

[pawlean (Pauline P. Narvas)]

In case this is related, we just shipped pnpm v10 support.

Automatic pnpm v10 support - Vercel