How to Fix EACCES: Permission Denied in npm

You run npm install -g to install a CLI tool, and instead of a clean install, you get this:

npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'

This npm EACCES error is one of the most common Node.js permission errors developers hit on macOS and Linux. Here’s why it happens and how to fix it properly.

Why npm Permission Denied Errors Happen

When you run npm install -g, npm writes to a system-level directory like /usr/local/lib/node_modules. If you installed Node.js using an official installer or a system package manager, that directory is typically owned by root. Your regular user account doesn’t have write access to it, so the install fails.

This is a security feature of Unix-based systems, not a bug. The fix isn’t to override those protections — it’s to give npm a location your user already owns.

Important distinction: This article covers global install permission errors. If you’re seeing permission errors inside a local project’s node_modules folder, the cause is different — usually a file ownership mismatch in your project directory.

Fix npm Global Install Permissions: Two Safe Approaches

Option 1: Reinstall Node.js Using a Version Manager (Recommended)

npm officially recommends using a Node version manager like nvm to avoid EACCES errors entirely. When nvm installs Node, it places everything inside your home directory — a location your user owns by default. No root access needed, ever.

Install nvm:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/HEAD/install.sh | bash

Then install Node:

nvm install --lts

After that, npm install -g works without sudo or permission changes. As a bonus, nvm lets you switch between Node versions per project — something no other fix offers.

Note: If you already have a custom npm prefix configured, nvm manages its own prefix internally. Don’t combine both approaches in the same environment, as they can conflict.

Option 2: Configure a User-Owned npm Global Directory

If you’d rather not use nvm, you can redirect npm’s global install location to a directory your user owns. This is the alternative described in the official npm docs.

mkdir ~/.npm-global
npm config set prefix '~/.npm-global'

Then add the bin directory to your PATH. For bash, add this to ~/.profile or ~/.bashrc:

export PATH=~/.npm-global/bin:$PATH

For zsh, add the same line to ~/.zshrc, then reload:

source ~/.zshrc

Verify it works by installing a package without sudo:

npm install -g npm-check-updates

What About sudo npm install -g?

Avoid it. Running sudo with npm installs files owned by root, which creates further permission problems down the line and introduces real security risks — a malicious or compromised package runs with elevated privileges. It’s a short-term workaround that makes things worse.

A Quick Alternative: Use npx Instead

If you only need a CLI tool occasionally, you may not need a global install at all. npx runs packages without installing them globally, using a local package or fetching one temporarily:

npm create vite@latest

No permissions required, no global directory involved.

Which Fix Should You Use?

Conclusion

The root cause of npm install -g EACCES errors is almost always the same: npm is trying to write to a root-owned directory. Fix that mismatch at the source — either by using nvm or by pointing npm to a directory you own — and the error disappears for good.

FAQs

Gain control over your UX

See how users are using your site as if you were sitting next to them, learn and iterate faster with OpenReplay. — the open-source session replay tool for developers. Self-host it in minutes, and have complete control over your customer data. Check our GitHub repo and join the thousands of developers in our community.