npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Unhandled Rejection Errors

"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"


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


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.


Sir, you just saved my life