npm ERR! code EEXIST — EEXIST: file already exists, symlink '../lib/node_modules/x/bin/x' -> '/usr/local/bin/x'
A global install can’t create its command link because a file with that name already exists.
Exact message you may see
EEXIST: file already exists, symlinknpm ERR! code EEXIST
Seen on:
npm
Meaning
Another installation (Homebrew, a different Node version, or an older global package) owns the binary name.
Common causes
- Binary installed by Homebrew/another manager
- Leftover link from an old global install
⚡ Quick fix
- npm install -g pkg --force to overwrite
- Remove the old binary/package first
- Use a Node version manager to avoid clashes
Detailed fix by platform
npm
npm uninstall -g yarn && npm install -g yarn
How to diagnose
- Path — Which binary exists and who installed it?
- 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
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 14 Oct 2026