npm ERR! code ENOTEMPTY

What This Error Means

npm tried to remove a directory that is not empty (ENOTEMPTY).

How to Fix It

1. Identify the path npm is failing on (look for the last referenced file path in the error output).
2. Delete the target directory manually (common offender: node_modules) and retry the install.
3. 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

1. Re-run the original command and confirm the filesystem error no longer appears.
2. If this is a permission fix, confirm new files in node_modules are owned by the expected user.

Manual filesystem checks

1. If a directory removal fails, confirm no process is using it (platform-specific: lsof +D <dir>).

Common CLI Output

npm ERR! code ENOTEMPTY

Prevention 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

        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)
    }