What does npm:ENOSPC mean?

npm hit ENOSPC because the disk ran out of free space while extracting packages, writing cache data, or updating node_modules.

npm ERR! code ENOSPC

Q: How do I prevent npm:ENOSPC in CI?

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.

Fix it fast

Most likely: The filesystem that holds the project, npm cache, temp folder, or CI workspace ran out of free space.

1. Confirm this is your error

npm ERR! code ENOSPC

2. Check the cause

df -h
npm config get cache
du -sh node_modules ~/.npm 2>/dev/null
ls -la <failing-path>

3. Apply the safe fix

# Free space on the filesystem shown in the error, then verify npm cache state.
npm cache verify
npm install

# In CI, increase the runner disk size or clear build artifacts before installing.

4. Verify it works

df -h
npm install

Don't use unsafe shortcuts

Do not retry repeatedly while the disk is still full.
Do not change package versions to fix ENOSPC, npm needs writable space.
Do not clean unrelated system folders before identifying which filesystem is full.

What Local Operation Failed

The remote service may be fine. This class of error is usually about what the local machine was allowed to read, write, cache, or execute.

Fix the local path, cache, or permissions

Identify the path npm is failing on (look for the last referenced file path in the error output).

Free disk space and retry. Also check Docker/CI runner disk quotas if this happens in CI.

Retry after cleaning local state when safe (common:remove node_modules and retry install).

Manual filesystem checks

Check disk space:df -h

Why the Local Machine Blocked It

The filesystem ran out of space while npm was extracting/writing files.

Verify the Local Path Is Usable Again

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.

How npm writes files during install

npm got far enough to read or write local state, but the host filesystem blocked the operation. Ownership drift, read-only mounts, stale caches, full disks, and restrictive permissions all show up in this layer. These are usually local machine or runner problems rather than upstream service problems, so fix the path, ownership, or free space before changing dependency versions.

Prevent Local State Drift

To prevent this, 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, and ensure CI runners have enough disk space and sensible file descriptor limits.

Docs and source code

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