What does npm:EMFILE mean?

npm hit EMFILE because the process opened too many files at once and exceeded the per-process file descriptor limit.

npm ERR! code EMFILE

Q: How do I prevent npm:EMFILE 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.

Q: How can I manually validate npm:EMFILE?

Check file descriptor limits: `ulimit -n`.

Fix it fast

Most likely: The npm process opened too many files at once and hit the per-process file descriptor limit.

1. Confirm this is your error

npm ERR! code EMFILE

2. Check the cause

ulimit -n
npm config get cache
ps aux | grep npm
lsof -p <npm-process-id> | wc -l

3. Apply the safe fix

# Raise the open-file limit for this shell, then retry.
ulimit -n 4096
npm install

# Also stop editors, watchers, and duplicate npm processes that are holding many files open.

4. Verify it works

ulimit -n
npm install

Don't use unsafe shortcuts

Do not delete the lockfile or change dependencies for EMFILE, it is an OS file-handle limit.
Do not run several installs or watchers against the same repo while debugging this.
Do not use sudo npm install as the fix, it does not solve the descriptor limit and may create permission problems.

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

Increase open file limits (ulimit -n) and retry. Also close background tools that watch many files.

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

Manual filesystem checks

Check file descriptor limits:ulimit -n

Why the Local Machine Blocked It

The process (or system) hit open file limits while npm was reading/writing many 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)
    }