"npm start" permission denied error: how to solve it?

Gabriel Guerra
Mar 15 · 1 min read

Weird, strange or annoying errors are part of our lives as miserable developers we are. :)

To all of you beginners in the black art, I'll share a quick antidote for this curse.

Most of cases are related to a bad Node installation or maybe related to the modules your [wrongly] are copying and pasting from another project.

So, to solve this issue all you have to do is:

  1. Remove Node
    If in OSX run brew uninstall node
  2. Delete the dir node_modules
  3. Install Node again globally
    Again, if in OSX run brew install -g node
  4. Run npm install
  5. Grab a cup of coffee
  6. Run npm start and feel a smile growing slowly in your face
Image licensing and credits

Everything's fine now!

You can go back to your happy coding :)

Gabriel Guerra

Written by

Creative FullStack Developer

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade