We have a situation where a vendor offers a library that has the same name as one on the public npm registry, but we have to install it from a private registry;
npm install foo --registry=https://someprivateregistry works, but people keep trying to add
foo to their package.json which causes the public one to be installed. If this were a scoped module, we could configure .npmrc to override
@scope but it’s not. It’s just called
Is there a way to configure
.npmrc so that it targets a registry for a plain-named, non-scoped package?