EACCES issue with npm@5.4
See original GitHub issueOSX 10.12.4 Node v8.4.0
npm 5.4
introduces permission errors when using node-notifier
. Cannot use node-notifier
if installed with npm 5.4
. Probably something to do with new npm, but filing just in case this is relevant to node-notifier
itself.
To replicate
> npm i -g npm@5.3
> npm i node-notifier
// index.js
const notifier = require('node-notifier');
notifier.notify('Message');
notifier.notify({
'title': 'My notification',
'message': 'Hello, there!'
});
> node index.js
(system notification appears. Works).
> npm i -g npm@5.4
> npm i node-notifier
>node index.js
Error: spawn EACCES
at _errnoException (util.js:1041:11)
at ChildProcess.spawn (internal/child_process.js:325:11)
at exports.spawn (child_process.js:493:9)
at Object.exports.execFile (child_process.js:208:15)
at Object.module.exports.fileCommandJson (Desktop/temp/eaccess_npm5.4/node_modules/node-notifier/lib/utils.js:79:13)
at NotificationCenter.notify (Desktop/temp/eaccess_npm5.4/node_modules/node-notifier/notifiers/notificationcenter.js:87:20)
at Object.<anonymous> (Desktop/temp/eaccess_npm5.4/index.js:3:10)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
> npm i -g npm@5.3
> node index.js
Error: spawn EACCES
at _errnoException (util.js:1041:11)
at ChildProcess.spawn (internal/child_process.js:325:11)
at exports.spawn (child_process.js:493:9)
at Object.exports.execFile (child_process.js:208:15)
at Object.module.exports.fileCommandJson (Desktop/temp/eaccess_npm5.4/node_modules/node-notifier/lib/utils.js:79:13)
at NotificationCenter.notify (Desktop/temp/eaccess_npm5.4/node_modules/node-notifier/notifiers/notificationcenter.js:87:20)
at Object.<anonymous> (Desktop/temp/eaccess_npm5.4/index.js:3:10)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
> npm i node-notifier
> node index.js
(works)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
npm ERR! Error: EACCES: permission denied - Stack Overflow
The weird thing is that I can install other packages with no issues, I just installed react-hook-form for example. I don't really know...
Read more >NPM5 Permissions Issue · Issue #16896 · npm/npm - GitHub
I access the npm registry via a VPN; I don't use a proxy, but have limited or unreliable internet access. Container:.
Read more >Resolving EACCES permissions errors when installing ...
This is the best way to avoid permissions issues. To reinstall npm with a node version manager, follow the steps in "Downloading and...
Read more >NPM Install - Resolving EACCES Permissions Denied
How to resolve eacces permissions denied when installing npm packages globally. Here's how you solve this issue in a couple of minutes.
Read more >Node 8 and npm@5 release: What's new?
Node 8.0.0 and npm@5 were released a few days ago. Learn what's new in Node ... Auth0 issues JSON Web Tokens on every...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just a heads up to anyone who get’s here - nvm v5.4.1 does fix it, but you have to reinstall your node_modules.
@mikaelbr Good eye! Looks like npm v5.4.1 fixes it too: https://github.com/npm/npm/releases/tag/v5.4.1