How to fix npm throwing error without sudo?

When you encounter permission or EACCES errors while running npm commands (like npm install -g <package>), you may be tempted to prefix your commands with sudo. However, that can lead to more permission headaches in the long run. Below are the recommended approaches to fix these issues so that you can run npm without sudo on macOS, Linux, or other UNIX-like systems.

1. Use a Node Version Manager (Recommended)

A Node Version Manager (like nvm) keeps Node.js (and npm) in your home directory, removing the need for global installations that conflict with system directories.

Install nvm:

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

(Check the nvm GitHub repo for updated commands.)

Install Node.js using nvm:

nvm install node      # Installs latest current version
nvm install --lts     # Installs latest LTS version

Use Node.js from nvm:

nvm use node
nvm alias default node   # Make it the default in new shells

Install Packages without sudo:
```
npm install -g <package>
```
Since nvm installs Node.js and npm in your user directory, you won’t need sudo for global installs.

2. Change npm’s Global Directory (Without nvm)

If you aren’t using a version manager, you can still configure npm to use a directory in your home folder for global installs:

Create a folder (e.g., ~/.npm-global) to store globally installed packages:
```
mkdir ~/.npm-global
```
Tell npm to use this folder as its global directory:
```
npm config set prefix '~/.npm-global'
```

Update your shell’s PATH so the executables can be found:

echo 'export PATH=$PATH:~/.npm-global/bin' >> ~/.bashrc
# For zsh:
# echo 'export PATH=$PATH:~/.npm-global/bin' >> ~/.zshrc
# Then reload your shell:
source ~/.bashrc

Install packages globally (without sudo):
```
npm install -g <package>
```

3. Fix Permissions of Your Existing npm Directories

If you’ve installed Node.js from a package manager (e.g., apt on Ubuntu) and are facing permission issues, you can try fixing them by:

Identifying your global npm directory. Run:
```
npm root -g
```
This might return something like /usr/local/lib/node_modules or /usr/lib/node_modules.
Change ownership of that directory to your user:
```
sudo chown -R $(whoami) $(npm root -g)
```
Check if your global bin directory is also in a root-owned path, like /usr/local/bin. If so, you can also change permissions accordingly—but use caution, as this might affect other system processes.

Important Note: Overriding system directories can create conflicts if your OS package manager also installs or manages Node packages.

4. Use `npx` for One-Off Commands

If you just need to run a CLI tool once (instead of installing it globally), npx can execute packages directly from npm without installing them to your system:

npx create-react-app my-app

This bypasses any global permission issues since npx fetches and runs the tool in a temporary environment.

Recommended Resource

Grokking JavaScript Fundamentals

5. Summary and Best Practices

Best Practice: Use nvm (or nvm-windows on Windows). This approach sidesteps system-level permission issues by installing Node.js and npm in your user directory.
Alternate Approach: Adjust npm’s prefix to a folder in your home directory (~/.npm-global).
Permissions: If you must use a system-installed Node, fix the ownership of npm’s global install directories—but be cautious with system directories.
Avoid sudo npm install -g: Using sudo can lead to further permission conflicts and is generally discouraged unless absolutely necessary.
Use npx for running CLI commands once or occasionally, so you don’t need to install them globally at all.

Following these recommendations should prevent most permission errors and allow you to use npm without sudo, making your development setup more secure and maintainable.

CONTRIBUTOR

TechGrind