Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • I deleted the node_modules and package-lock.json folders and then typed npm i on the command line. After that, everything was fine. Commented Apr 21, 2021 at 12:22
  • sometimes, you might not have node_modules folder at all, maybe fresh clone. run npm install first. Commented May 26, 2021 at 23:22
  • Do you have folder node_modules ? For me the same error happened, when I cloned my Angular project through GitHub on different laptop. I didn't push folder node_modules to save space. Because I was on cell phone tethering, I decided do not reinstall all packages, but copy node_modules folder from different project on the same laptop. And it worked! Commented Sep 8, 2021 at 19:10
  • 3
    So many identical answers to this question. Commented Nov 25, 2021 at 16:45
  • 3
    @SteveSmith I've already flagged a few, but if you notice such answers in the future, you can custom flag them and leave a link to the original answer to get them cleaned up. Commented Dec 14, 2021 at 20:28