Let’s say you want to override the global registry configured in your. a sibling to the package.json and node_modules). npmrc with the values that you want in the root of the project (i.e. To override any global settings, all you need to do is create a more local. npmrc which comes with all of the same warnings that having global anything comes with. npmrc plays and I set about fixing it.įirst of all - worth mentioning: You can have a global. This was the first time I realized the role the. The issue, it turned out (after a lot of head scratching) was that the package lock pointed to a private registry as the first place to look, but that computer didn’t have access to that registry. Then I tried working on it on another machine to find that I couldn’t install any of the packages. I was working on a project recently and did the initial set up on one computer. When Something You Thought Worked, Stops & Global Configs This one, as you might expect from its name, for NPM.

npmrc, a file I didn’t even know existed. The issue, it turned out had to do with my. That was the situation recently with npm, the reliable workhorse behind node projects. When things that used to work break, I want to understand why.

Npm config set registry default