Resolving EACCES permissions errors when installing packages globally
See Details
Table of contents
If you see anEACCES error when you try toinstall a package globally, you can either:
Reinstall npm with a node version manager (recommended),
or
Manually change npm's default directory
Reinstall npm with a node version manager
This is the best way to avoid permissions issues. To reinstall npm with a node version manager, follow the steps in "Downloading and installing Node.js and npm". You do not need to remove your current version of npm or Node.js before installing a node version manager.
Manually change npm's default directory
Note: This section does not apply to Microsoft Windows.
To minimize the chance of permissions errors, you can configure npm to use a different directory. In this example, you will create and use a hidden directory in your home directory.
Configure npm to use the new directory path:
npm config set prefix ~/.localIn your preferred text editor, open or create a
~/.profilefile and add this line:PATH=~/.local/bin:$PATHIf you are using zsh (which you can find out by running
echo $0), you will also need to add this line to~/.zprofile:source ~/.profileOn the command line, update your system variables:
source ~/.profileTo test your new configuration, install a package globally without using
sudo:npm install -g npm-check-updatesAnd run it:
ncu -g
npx: an alternative to running global commands
If you are using npm version 5.2 or greater, you may want to considernpx as an alternative way to run global commands, especially if you only need a command occasionally. For more information, seethis article about npx.
