npm ERR! code EACCESS by installing @angular/cli

Question

Environment:

Ubuntu 16.04
node v8.11.1 (installed with package manager)
npm v5.6.0

After the clean installation of npm and trying to install @angular/cli

npm install -g @angular/cli

I'm getting an error related with EACCESS that it is probably related with permissions because it disappears with root access. The thing is that it is not recommended to use it that way, so how could I solve this?

Console ERROR

$ npm install -g @angular/cli
npm WARN checkPermissions Missing write access to /usr/lib/node_modules
npm ERR! path /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!  { Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!   stack: 'Error: EACCES: permission denied, access \'/usr/lib/node_modules\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/lib/node_modules' }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2018-04-25T15_23_36_781Z-debug.log

File .npm/_logs/2018-04-25T15_23_36_781Z-debug.log

2566 warn checkPermissions Missing write access to /usr/lib/node_modules
2567 verbose stack Error: EACCES: permission denied, access '/usr/lib/node_modules'
2568 verbose cwd /opt/workspace/roscam-front
2569 verbose Linux 2.6.32-042stab120.19
2570 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "@angular/cli"
2571 verbose node v8.11.1
2572 verbose npm  v5.6.0
2573 error path /usr/lib/node_modules
2574 error code EACCES
2575 error errno -13
2576 error syscall access
2577 error Error: EACCES: permission denied, access '/usr/lib/node_modules'
2577 error  { Error: EACCES: permission denied, access '/usr/lib/node_modules'
2577 error   stack: 'Error: EACCES: permission denied, access \'/usr/lib/node_modules\'',
2577 error   errno: -13,
2577 error   code: 'EACCES',
2577 error   syscall: 'access',
2577 error   path: '/usr/lib/node_modules' }
2578 error Please try running this command again as root/Administrator.
2579 verbose exit [ -13, true ]

Not recommended? Is says right there in the error Please try running this command again as root/Administrator. It may not be ideal, but it is recommended. — R. Richards
– R. Richards, Commented Apr 25, 2018 at 16:08
Yes, it's a kind of misleading. I guess that that will be the default and easy to pass through this issue, but npm documentation recommends change default directory to prevent permissions errors — Joe
– Joe, Commented Apr 25, 2018 at 16:13

Rob · Accepted Answer · 2018-04-27 02:41:49Z

2

One option to deal with this problem will be to change npm's default directory to use a different directory.

We need to make a directory for global installations, in this example inside user directory:
```
mkdir ~/.npm-global
```
We configure npm to use the new directory path:
```
npm config set prefix '~/.npm-global'
```
Open or create a ~/.profile file and add this line:
```
export PATH=~/.npm-global/bin:$PATH
```
We update your system variables:
```
source ~/.profile
```

Now we can test by installing a package globally without using root permissions.

npm install -g jsonfile

Another option to avoid all these steps and modifying ~/.profile, it will be by defining an ENV variable with the following command(:

NPM_CONFIG_PREFIX=~/.npm-global

npm reference

edited Apr 27, 2018 at 2:41

Rob♦

27.5k16 gold badges89 silver badges103 bronze badges

answered Apr 25, 2018 at 17:06

Joe

7,93920 gold badges70 silver badges115 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Kyle Vassella Over a year ago

Step 3 says to Open or create a ~/.profile file - can you explain how to do this part of the step?

timotom · Accepted Answer · 2019-07-11 22:42:55Z

0

I had the EACCES permission error too. I did a fresh install of Ubuntu 18.04. The 16.04 version may not be much different. It all works for me. Hope this helps.

----------- FOR YOU, YOU SHOULD APPLY THIS CODE FROM HERE

sudo apt-get install curl software-properties-common
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt install nodejs
node -v
npm -v
npm init
whoami

which npm              # returned /usr/bin
npm config get prefix  # returned /usr
npm config set prefix /usr/bin
npm config get prefix
ls -la /usr/bin/npm    # has a symbolic link to ../lib/node_modules/npm/bin/npm-cli.js
sudo chown -R your_user /usr/bin/npm   # NOT /usr/bin or we lock out sudo too!!!!
sudo chown -R your_user app-folder/
ls -la /usr/bin/npm
npm init  # I was curious to see if this still works
npm install  # WORKS GREAT!!! No need for sudo now.:)

----------- TO THERE

THIS IS THE USE CASE I WORKED ON AFTER I INSTALLED THE ABOVE. YOURS SHALL WORK TOO IF THE ABOVE IS WELL SET UP.

npm start # script
npm run start:prod  # works as well
npm i debug --save-dev     # works but need to install 'make'
sudo apt install build-essential
npm i debug --save-dev    # installed and launched successfully!

Note: if you were to install npm i debug --global instead, you may still get that EACCES permission error as your local user will not be able to access root permissions elsewhere in your file system. That's why we use 'change ownership' (i.e. chown your_user: see above in the code).

edited Jul 11, 2019 at 22:42

answered Jul 11, 2019 at 22:37

timotom

753 silver badges13 bronze badges

1 Comment

timotom Over a year ago

I based and compiled my solution above on this video: youtube.com/watch?v=bxvybxYFq2o

Collectives™ on Stack Overflow

npm ERR! code EACCESS by installing @angular/cli

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related