npm ERR! The `npm ci` command can only install with an existing package-lock.json or npm-shrinkwrap.json
npm ci needs a committed lockfile and didn’t find one.
Exact message you may see
can only install with an existing package-lock.json
Seen on:
npm
Meaning
Lockfile not committed (gitignored), or the project uses yarn/pnpm lockfiles instead.
Common causes
- package-lock.json in .gitignore
- Project uses yarn.lock or pnpm-lock.yaml
⚡ Quick fix
- Generate and commit package-lock.json
- Use the project’s package manager in CI (yarn install --frozen-lockfile, pnpm install --frozen-lockfile)
Detailed fix by platform
npm
npm install --package-lock-only && git add package-lock.json
How to diagnose
- Files — Which lockfile exists?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AADSTS70021 AADSTS70021: No matching federated identity record found for presented assertion (GitHub Actions / workload identity)
- Command CodeSign failed Command CodeSign failed with a nonzero exit code (errSecInternalComponent / resource fork, Finder information not allowed)
- EINTEGRITY npm ERR! code EINTEGRITY — sha512 integrity checksum failed
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026