npm ERR! code ENOTEMPTY — ENOTEMPTY: directory not empty, rename
npm couldn’t rename a folder in node_modules because it wasn’t empty — usually a corrupted or concurrently modified node_modules.
ENOTEMPTY: directory not emptycode ENOTEMPTY Meaning
Interrupted installs, two npm processes at once, or antivirus/indexers locking files leave node_modules in a broken state.
Common causes
- Interrupted previous install
- Two installs running simultaneously
- Antivirus/file sync locking files
⚡ Quick fix
- Delete node_modules and reinstall
- Make sure no other npm/IDE process is installing
- Exclude the project from file sync/antivirus
Detailed fix by platform
npm
rm -rf node_modules && npm cache verify && npm ci
How to diagnose
- Processes — Another npm running?
- State — Interrupted install?
🔧 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.
Report a correction or suggest an improvement
Last updated 13 Oct 2026