What Local Operation Failed
npm hit EISDIR because it expected a file path, but the target resolved to a directory instead, so npm could not read or write it correctly.
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).
Make sure you are running npm in the right directory (the one with package.json).
If the missing path is under node_modules, remove node_modules and reinstall.
Retry after cleaning local state when safe (common:remove node_modules and retry install).
Manual filesystem checks
Confirm package.json exists in the current directory: ls -la package.json.
Why the Local Machine Blocked It
npm referenced a path that does not exist (wrong working directory, stale node_modules, or a broken install state).
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.
Examples
npm ERR! code EISDIRDocs 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)
}