npm ERR! code EJSONPARSE — Failed to parse json / Unexpected token in JSON at position
package.json (or package-lock.json) contains invalid 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 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