NextJS Deployment crashing with ERR_PNPM_NO_LOCKFILE
linearly
PROOP

2 years ago

Project ID: 31d9b86c-db7f-44b7-8a2b-6d81ce651e2a

Basically the same as https://help.railway.app/questions/deployment-of-next-js-project-has-suddenl-31fd443e and the other ERR_PNPM issue.

My project is crashing with:

1.881  ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent

I have tried:
❌ Using pnpm v8 by having this in my package.json:

"packageManager": "pnpm@8.10.0"

I actually never used v9.

❌ Using pnpm@latest as so:

"packageManager": "pnpm@latest"

This actually resulted in another error saying this format is invalid:

0.535 Usage Error: Invalid package manager specification in package.json (pnpm@latest); expected a semver version

❌ Trying both the V2 and the Legacy runtime

❌ Deleting/Regenrating node_modules and pnpm-lock.yaml

What can I do?

2 Replies

linearly
PROOP

2 years ago

Fixed it. Turns out I was using pnpm v9 locally to generate the lockfile and that was the issue. So even though I specified v8 in package.json, the fix was to downgrade my local pnpm to v8 and reinstall all dependencies


2 years ago

specifying pnpm v9 or @latest as shown here does work -


Loading...