npm WARN old lockfile — The package-lock.json file was created with an old version of npm, so supplemental metadata must be fetched
The lockfile is lockfileVersion 1 (npm 6) and npm 7+ is upgrading it.
Seen on:
npm
Meaning
Harmless but slow the first time. Commit the upgraded lockfile so it doesn’t repeat.
Common causes
- Lockfile created by npm 6
- Team members on different npm versions
⚡ Quick fix
- Run npm install once and commit the updated lockfile
- Standardise npm versions
Detailed fix by platform
npm
npm install && git add package-lock.json
How to diagnose
- Version — lockfileVersion in package-lock.json
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🧠 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026