Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

I have the following package.json

{
  "name": "@test/test"
  "dependencies": {
    "@test/foo": "^0.3.3",
    "@test/bar": "^0.3.0"
  }
}

I have a private registry (verdaccio on npm.example.com) setup with the @test scope, in the registry there is following versions

• @test/foo: 0.3.3 and 0.4.0-test.1
• @test/bar: 0.3.0 and 0.4.0-test.1

The 0.3.x releases are tagged with latest and the 0.4.0-test.1 releases are tagged as beta

Running npm install --registry=https://npm.example.com --tag beta installs the 0.3.x not the 0.4.0-test.1

From the npm install docs

The --tag argument will apply to all of the specified install targets. If a tag with the given name exists, the tagged version is preferred over newer versions.

Expected Behavior

With the beta tag added to the command line I expect 0.4.0-test.1 versions to be installed as they have the matching tag.

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm: 8.5.0
• Node.js: v16.14.1
• OS Name: Linux (Fedora 35)
• System Model Name: Think Pad X1 Carbon
• npm config:

; "global" config from /usr/etc/npmrc

prefix = "/usr/local" 
python = "/usr/bin/python3" 

; "user" config from /home/hardillb/.npmrc

//@test:registry = "https://npm.example.com/" 
//npm.example.com/:_authToken = (protected) 

; node bin location = /usr/bin/node
; cwd = /opt/share/projects/flowforge/test/ff
; HOME = /home/hardillb
; Run `npm config ls -l` to show all defaults.