npm ERR! code EJSONPARSE — Failed to parse json / Unexpected token in JSON at position
package.json (or package-lock.json) contains invalid JSON.
Exact message you may see
code EJSONPARSEFailed to parse jsonpackage.json must be actual JSON
Seen on:
npm
Meaning
Trailing commas, comments, merge-conflict markers or a manual edit typo break npm entirely.
Common causes
- Trailing comma
- Comments in package.json
- Merge conflict markers (<<<<<<<) in package-lock.json
- Smart quotes
⚡ Quick fix
- Validate the file (JSON error finder / npx jsonlint)
- Resolve lockfile conflicts by regenerating: delete it and npm install
Detailed fix by platform
npm
git checkout --theirs package-lock.json && npm install # regenerate after conflict
How to diagnose
- File — package.json or lockfile?
- Line — Position in the message
🔧 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
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 15 Oct 2026