Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


eaccess permission denied when trying to use yo #1097

mgenev opened this Issue · 3 comments

3 participants


Please help! I used to have the old installation with curl and homebrew, then 1.0 came out and I installed with "npm install -g yo grunt-cli bower". It didn't work so I did "sudo chown -R $USER /usr/local" then the installation seemingly completed, but when I tried to run yo, I get:

$ yo

Error: EACCES, permission denied '/Users/mgenev/.config/configstore/update-notifier-yo.yml'
at Object.fs.openSync (fs.js:427:18)
at Object.fs.writeFileSync (fs.js:966:15)
at Object.create.all.set (/usr/local/lib/node_modules/yo/node_modules/update-notifier/node_modules/configstore/configstore.js:39:7)
at Object.Configstore (/usr/local/lib/node_modules/yo/node_modules/update-notifier/node_modules/configstore/configstore.js:30:11)
at new UpdateNotifier (/usr/local/lib/node_modules/yo/node_modules/update-notifier/lib/update-notifier.js:23:16)
at module.exports (/usr/local/lib/node_modules/yo/node_modules/update-notifier/lib/update-notifier.js:124:23)
at Object. (/usr/local/lib/node_modules/yo/bin/yo:109:18)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)


Hi all,

You need to change /Users/mgenev/.config/configstore/update-notifier-yo.yml owner to your user name:
sudo chown yourusername:yourusername /Users/mgenev/.config/configstore/update-notifier-yo.yml

Typically you don't want to change to root but only sudo on your server.
That should fix the permission issue problem.



Thanks for explaining, @ariellephan. :cake: This is exactly what you should do.

@passy passy closed this

sudo chown yourusername:admin /Users/yourusername/.config/configstore/update-notifier-yo.yml

is what worked for me on os x, i needed to specify admin as the group.

@sindresorhus sindresorhus locked and limited conversation to collaborators
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Something went wrong with that request. Please try again.