What This Error Means
npm hit EPERM because the operating system denied the filesystem operation, commonly due to permissions, locks, antivirus, or Windows file handling.
How to Fix It
Identify the path npm is failing on (look for the last referenced file path in the error output).
Avoid sudo npm install for project installs. It often causes mixed ownership inside node_modules.
Fix ownership of npm cache and project folder (example:sudo chown -R $(whoami) ~/.npm).
If the error is for global installs, use a user-writable prefix (example:npm config set prefix ~/.npm-global) and ensure PATH includes it.
Retry after cleaning local state when safe (common:remove node_modules and retry install).
Why It Happens
The current user does not have permission to write to the project folder, npm cache, or global prefix.
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
Check ownership/permissions for the failing path:ls -la <path>
Examples
npm ERR! code EPERM
npm ERR! errno EPERMPrevention 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/workspaces/libnpmexec/lib/with-lock.js
Open-source npm CLI code reference tied to this error code. - GitHub
try {
await fs.mkdir(lockPath)
} catch (err) {
if (err.code !== 'EEXIST' && err.code !== 'EBUSY' && err.code !== 'EPERM') {
throw err
}