npm ERR! code ELSPROBLEMS — invalid / extraneous / missing packages in npm ls
npm ls found the installed tree doesn’t match package.json and the lockfile.
code ELSPROBLEMSUNMET DEPENDENCYinvalid: interpreted as Meaning
“invalid” means an installed version doesn’t satisfy the declared range, “extraneous” means installed but not declared, “missing” means declared but not installed. Often after manual edits, interrupted installs or mixing package managers.
Common causes
- Interrupted or partial install
- Manual edits to node_modules or package.json
- Mixing npm with yarn/pnpm in one project
- Peer dependency ranges not satisfied
⚡ Quick fix
- Reinstall cleanly: rm -rf node_modules && npm ci
- Remove extraneous packages: npm prune
- Fix ranges flagged as invalid
Detailed fix by platform
npm
npm ls --all 2>&1 | grep -E "invalid|missing|extraneous"
How to diagnose
- Problems — Which packages are listed?
- Lockfile — In sync with package.json?
🔧 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
- 0x8007007E 0x8007007E: The specified module could not be found
- Dependency requires compileSdk Dependency 'androidx.x:1.y' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs
- E404 npm ERR! code E404 — 404 Not Found: package@version is not in this registry
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.
Report a correction or suggest an improvement
Last updated 12 Oct 2026