What This Error Means
npm hit ENOTEMPTY because it tried to replace or remove a directory that still contains files, often during install, cleanup, or rename steps.
How to Fix It
Identify the path npm is failing on (look for the last referenced file path in the error output).
Delete the target directory manually (common offender:node_modules) and retry the install.
Retry after cleaning local state when safe (common:remove node_modules and retry install).
Why It Happens
A background process is locking files while npm is trying to rename/remove them.
How to Verify
Re-run the original command and confirm the filesystem error no longer appears.
If this is a permission fix, confirm new files in node_modules are owned by the expected user.
Manual filesystem checks
If a directory removal fails, confirm no process is using it (platform-specific:lsof +D <dir>).
Examples
npm ERR! code ENOTEMPTYPrevention Tips
Keep npm cache and project directories owned by the build user.
Avoid running project installs as root unless you know exactly why you need it.
Ensure CI runners have enough disk space and sensible file descriptor limits.
Where This Can Be Triggered
github.com/npm/cli/blob/417daa72b09c5129e7390cd12743ef31bf3ddb83/lib/commands/cache.js
This is a representative filesystem write path during npm operations. Filesystem codes like this are raised by Node/OS when this write fails. - GitHub
break
}
output.standard(`Deleted: ${key}`)
await cacache.rm.entry(cachePath, key)
// XXX this could leave other entries without content!
await cacache.rm.content(cachePath, entry.integrity)
}