[BUG] Changing NPM version when on 7.23.0 ignores registry option #3758
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Is there an existing issue for this?
Current Behavior
I use an internal network for development. Because of this, I have a mirror of the npm registry. After I updated npm to version 7.23.0 and attempted to downgrade npm to version 7.22.0 using
npm install --global npm@7.22.0
, I noticed the install would fail because npm was ignoring the registry I specified. This operation was forced to use the default registryhttps://registry.npmjs.org/npm
during one of it's checks.Expected Behavior
I would expect that if an alternative registry is provided, the npm install checks would use that registry and continue the install process.
Steps To Reproduce
a. Any OS without an internet connection that uses a mirror of the npm registry on an internal network.
b. Need to be using npm version 7.23.0.
npm install --global npm@7.22.0
Environment
The text was updated successfully, but these errors were encountered: