Unhandled Rejection Errors

(Kenneth Cannon) #1

"npm install
Unhandled rejection Error: EACCES: permission denied, rename β€˜/home/geekboyison/.npm/_cacache/tmp/f6e1f781’ -> β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/17/eb/ba8cb3285c906d859e8707e4e79795fb65e3’

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f2/33’ 621

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/1d/41’

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’

npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
Unhandled rejection Error: EACCES: permission denied, mkdir '/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’sers

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’ in

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’

Unhandled rejection Error: EACCES: permission denied, mkdir β€˜/home/geekboyison/.npm/_cacache/content-v2/sha1/f8/6e’

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! https://npm.community"

0 Likes

(Kiera Manion-Fischer) #2

Hi there, thanks for sharing this, and my apologies for the delayed response. If you’re not using the latest version of npm, I’d recommend upgrading using npm install npm@latest -g If you’re still having issues, please share your entire npm-debug.log output. You can learn more about how to generate that here: https://docs.npmjs.com/generating-and-locating-npm-debug-log-files

0 Likes

(John Gee) #3

The advice from @kiera is sound, but I can probably jump ahead to a work-around.

This is likely an ownership issue left behind by using sudo with global installs. The short answer is try:

sudo chown -R $(whoami) ~/.npm

The canonical bug is: Global installs (sudo npm i -g) fail on Mac after 6.5 upgrade. Works fine after 6.4.1 downgrade.

1 Like

(Alvin J Choi) #4

Sir, you just saved my life

1 Like

(system) closed #5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

0 Likes