DEV Community

Sh Raj
Sh Raj

Posted on

Resolving npm EACCES Errors: Fixing Permissions to Install Global Packages

Resolving npm EACCES Errors: Fixing Permissions to Install Global Packages

In the world of Node.js development, npm (Node Package Manager) is a powerful tool that allows developers to easily manage packages and dependencies for their projects. However, sometimes when attempting to install packages globally using npm, you might encounter an "EACCES" error, indicating a permission issue. This guide will walk you through the steps to resolve these errors and successfully install global npm packages.

Understanding the EACCES Error

The "EACCES" error occurs when npm is unable to create symlinks or write to certain directories due to insufficient permissions. This commonly happens when trying to install packages globally without the necessary privileges.

shaswatraj@Sh shadev3 % npm i -g pnpm

npm ERR! code EACCES
npm ERR! syscall symlink
npm ERR! path ../lib/node_modules/pnpm/bin/pnpm.cjs
npm ERR! dest /usr/local/bin/pnpm
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, symlink '../lib/node_modules/pnpm/bin/pnpm.cjs' -> '/usr/local/bin/pnpm'
npm ERR!  [Error: EACCES: permission denied, symlink '../lib/node_modules/pnpm/bin/pnpm.cjs' -> '/usr/local/bin/pnpm'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'symlink',
npm ERR!   path: '../lib/node_modules/pnpm/bin/pnpm.cjs',
npm ERR!   dest: '/usr/local/bin/pnpm'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in: /Users/shaswatraj/.npm/_logs/2024-04-17T15_45_23_875Z-debug-0.log
shaswatraj@Sh shadev3 % 
Enter fullscreen mode Exit fullscreen mode

Option 1: Using sudo (Superuser Do)

The simplest way to bypass permission issues is to use sudo before the npm command. For example:

sudo npm i -g <package-name>
Enter fullscreen mode Exit fullscreen mode

By prefixing the command with sudo, you are running it with superuser privileges, allowing npm to perform the installation without permission errors. However, it's crucial to exercise caution when using sudo, as it grants extensive access and should only be used when necessary.

Option 2: Fixing Permissions

A more secure approach is to fix the permissions of the directories where npm installs global packages. Here's how:

  1. Change Ownership of /usr/local Directory:
   sudo chown -R $(whoami) /usr/local
Enter fullscreen mode Exit fullscreen mode

This command changes the ownership of the /usr/local directory and its subdirectories to your user, enabling npm to install global packages without requiring sudo.

  1. Change Ownership of npm Directories:
   sudo chown -R $(whoami) ~/.npm
   sudo chown -R $(whoami) ~/.config
Enter fullscreen mode Exit fullscreen mode

These commands ensure that npm has the necessary permissions for its cache and configuration directories.

  1. Install Global Package: Once permissions are updated, you can install global npm packages without sudo:
   npm i -g <package-name>
Enter fullscreen mode Exit fullscreen mode

Now npm should be able to create symlinks and write to the necessary directories without encountering permission errors.


Encountering "EACCES" errors when installing npm packages globally can be frustrating, but understanding how to manage permissions effectively can resolve these issues. While using sudo is a quick fix, it's recommended to adjust directory ownerships to ensure a more secure and seamless npm experience. With the steps outlined above, you can overcome permission hurdles and continue building amazing projects with Node.js and npm.

Remember, when working with system-level permissions, it's important to proceed with caution to avoid unintended consequences. Always ensure you understand the commands you're using and their implications on your system.

Top comments (0)