What This Error Means
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.
How to Fix It
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).
Why It Happens
npm referenced a path that does not exist (wrong working directory, stale node_modules, or a broken install state).
How to Verify
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.
Manual filesystem checks
Confirm package.json exists in the current directory: ls -la package.json.
Examples
npm ERR! code EISDIRPrevention 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
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)
}