How to Fix "npm ERR! code EACCES" Permission Errors (2026 Guide)

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

If you're seeing this error, don't just run sudo npm install. That's a temporary fix that creates bigger problems later. I'll show you 5 proper solutions, ranked from best to worst.

Why This Error Happens

When you install Node.js using the official installer or a package manager, it often places global packages in directories like:

• /usr/local/lib/node_modules (macOS/Linux)
• /usr/lib/node_modules (Linux)
• C:\Program Files\nodejs\node_modules (Windows)

These directories are owned by root/administrator, so your regular user account can't write to them without elevated permissions.

Solution 1: Use a Node Version Manager (Recommended)

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

source ~/.zshrc  # or ~/.bash_profile

nvm install --lts
nvm use --lts

npm install -g typescript  # No sudo needed!

echo 'nvm use --lts' >> ~/.zshrc

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

source ~/.bashrc

nvm install --lts
nvm use --lts

npm install -g typescript  # No sudo needed!

nvm install lts
nvm use lts

npm install -g typescript  # No admin needed!

Solution 2: Change npm's Default Directory

Step 1: Create a directory for global packages

mkdir ~/.npm-global

Step 2: Configure npm to use this directory

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

Step 3: Add to your PATH

For bash (Linux/macOS):

echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

For zsh (macOS):

echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.zshrc
source ~/.zshrc

Step 4: Test it

npm install -g typescript  # Should work without sudo

Solution 3: Use npx Instead of Global Installs

Instead of:

npm install -g create-react-app
create-react-app my-app

Use:

npx create-react-app my-app

Benefits:

• No global installation needed
• Always uses the latest version
• No permission issues
• Keeps your system clean

Common tools that work with npx:

• npx create-react-app
• npx create-next-app
• npx create-vite
• npx eslint
• npx prettier

Solution 4: Fix Permissions on Existing Installation

For macOS/Linux:

# Find npm's global directory
npm config get prefix

# Change ownership to your user (replace /usr/local with your prefix)
sudo chown -R $(whoami) /usr/local/lib/node_modules
sudo chown -R $(whoami) /usr/local/bin
sudo chown -R $(whoami) /usr/local/share

Solution 5: Use Homebrew (macOS Only)

Step 1: Uninstall existing Node (if installed via official installer)

# Remove Node.js installed from nodejs.org
sudo rm -rf /usr/local/bin/node
sudo rm -rf /usr/local/lib/node_modules

Step 2: Install Node via Homebrew

brew install node

Step 3: Test it

npm install -g typescript  # Should work without sudo

Which Solution Should You Use?

Preventing Future Permission Issues

Once you've fixed the issue, follow these best practices:

1. Never use sudo npm install - It creates more problems than it solves
2. Use a version manager - It's the cleanest solution
3. Prefer npx for one-time tools - Don't clutter your global packages
4. Use npm ci instead of npm install in CI/CD pipelines
5. Keep global packages minimal - Install most packages locally in projects

Troubleshooting Common Issues

"command not found" after installing globally

If you installed a package globally but can't run it:

# Check where global packages are installed
npm config get prefix

# Make sure the bin directory is in your PATH
echo $PATH

# Add it if missing (example for ~/.npm-global)
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.zshrc
source ~/.zshrc

Still getting permission errors after using nvm

This usually means you have an old Node installation conflicting:

# Check which node is being used
which node
which npm

# If it's not in ~/.nvm, uninstall the system Node
# macOS: Remove from /usr/local/bin
# Linux: sudo apt remove nodejs (or your package manager)
# Windows: Uninstall from Programs & Features

Summary

The EACCES error happens because npm is trying to write to a protected directory. The best solution is to use a Node version manager (nvm or nvm-windows), which installs Node in your home directory where you have full permissions.

Quick recap:

• ✅ Best solution: Use nvm/nvm-windows
• ✅ Quick alternative: Change npm's global directory
• ✅ Modern approach: Use npx instead of global installs
• ❌ Avoid: Using sudo npm install

Still having issues? Contact us and we'll help you troubleshoot.