npm "ENOTEMPTY: directory not empty, rename" - Fix Stale node_modules in CI

npm installs packages by staging them and renaming into place. ENOTEMPTY on that rename means the destination directory already had unexpected contents - a leftover from a stale node_modules, a restored partial cache, or a concurrent process.

What this error means

npm install/npm ci fails with ENOTEMPTY: directory not empty, rename ... pointing at a .staging or package path under node_modules. It often follows a restored cache or an interrupted previous install.

npm error code ENOTEMPTY
npm error syscall rename
npm error path /app/node_modules/.staging/lodash-XXXX
npm error dest /app/node_modules/lodash
npm error errno -39
npm error Error: ENOTEMPTY: directory not empty, rename '...' -> '...'

Common causes

A stale or partially populated node_modules

Leftover package directories from an interrupted install (or a restored partial cache) make the destination non-empty when npm tries to rename the staged copy in.

A concurrent process touching node_modules

A watcher, a parallel install, or antivirus holding files under node_modules can leave a directory non-empty at the moment of rename.

How to fix it

Start from a clean node_modules

Remove the existing tree and reinstall so the rename targets are empty.

rm -rf node_modules
npm cache verify
npm ci

Remove contention

1. Ensure no other step, watcher, or process touches node_modules during install.
2. Do not cache a partial node_modules across runs.
3. Run installs sequentially, not in parallel, for the same project.

How to prevent it

• Use npm ci so node_modules starts empty.
• Never cache or restore a partial node_modules.
• Avoid concurrent processes touching the module tree.

Related guides