What I Wanted to Do
Install packages using only our local private (selectively proxied) registry
What Happened Instead
npm attempts to install some packages from https://registry.npmjs.org
npm config set registry <our_private_registry_url>
npm install <package with package-lock.json and dependencies “resolved” to the public npmjs registry>
This issue on the previous github appears to be related, so I’m not the only one.
It would appear it’s deciding to used the registry the package was resolved to. That’s not the behavior I want. I want everything to go through our private registry.