[BUG] npm view --registry option not respected

[boutell]

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

If @mynamespace/my-tool exists in regular npm, but my root .npmrc looks like this:

//registry.npmjs.org/:_authToken=abcdef
//npm.portal.mycompany.dev/:_authToken=ghijkl
@mynamespace:registry=https://npm.portal.apos.dev

This command will yield output from npm.portal.mycompany.dev, even though registry.npmjs.org was explicitly specified by a command line option:

npm view @mynamespace/my-tool --json --registry=https://registry.npmjs.org

In other words, --registry is silently ignored by npm view.

There is no package-lock.json file in play here.

Expected Behavior

Output from the main npm registry, because --registry was expressly used to request that.

Steps To Reproduce

See above. I suggest that you publish clearly distinct version numbers to the two registries to simplify the test.

Environment

• npm: 10.9.0 (others tried)
• Node.js: 18.20.4
• OS Name: MacOS
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here
; "user" config from /Users/boutell/.npmrc

@apostrophecms-pro:registry = "https://npm.portal.apos.dev"
//npm.portal.apos.dev/:_authToken = (protected)
//registry.npmjs.org/:_authToken = (protected)

; node bin location = /Users/boutell/.nvm/versions/node/v18.20.4/bin/node
; node version = v18.20.4
; npm local prefix = /opt/ops-tools
; npm version = 10.9.0
; cwd = /opt/ops-tools
; HOME = /Users/boutell
; Run `npm config ls -l` to show all defaults.

[boutell]

Please note this is distinct from #3235 because package-lock.json is not involved.

[milaninfy]

@boutell I believe correct syntax for scoped registry is
npm view @mynamespace/my-tool --json --@mynamespace:registry=https://registry.npmjs.org

here is the output with correct syntax which points to correct registry setting

.npmrc

~/workarea/rep $ cat .npmrc
@mynamespace:registry=https://npm.portal.apos.dev

~/workarea/rep $ npm view @mynamespace/my-tool --json --@mynamespace:registry=https://registry.npmjs.org -dddd
npm info using npm@10.9.0
npm info using node@v22.9.0
npm http fetch GET 404 https://registry.npmjs.org/@mynamespace%2fmy-tool 1801ms (cache skip)
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@mynamespace%2fmy-tool - Not found
npm error 404
npm error 404  '@mynamespace/my-tool@*' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://registry.npmjs.org/@mynamespace%2fmy-tool - Not found",
    "detail": "'@mynamespace/my-tool@*' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}
npm error A complete log of this run can be found in: /Users/milaninfy/.npm/_logs/2024-11-20T15_17_38_894Z-debug-0.log

[boutell]

Neat, I had no idea that was a thing! Does this mean --registry has no effect at all?

…

On Wed, Nov 20, 2024 at 10:21 AM milaninfy ***@***.***> wrote: @boutell <https://github.com/boutell> I believe correct syntax for scoped registry is npm view @mynamespace/my-tool --json ***@***.***:registry= https://registry.npmjs.org here is the output with correct syntax which points to correct registry setting ~/workarea/rep $ npm view @mynamespace/my-tool --json ***@***.***:registry=https://registry.npmjs.org -dddd npm info using ***@***.*** npm info using ***@***.*** npm http fetch GET 404 ***@***.***%2fmy-tool 1801ms (cache skip) npm error code E404 npm error 404 Not Found - GET ***@***.***%2fmy-tool - Not found npm error 404 npm error 404 ***@***.***/my-tool@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. { "error": { "code": "E404", "summary": "Not Found - GET ***@***.***%2fmy-tool - Not found", "detail": ***@***.***/my-tool@*' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url." } } npm error A complete log of this run can be found in: /Users/milaninfy/.npm/_logs/2024-11-20T15_17_38_894Z-debug-0.log — Reply to this email directly, view it on GitHub <#7904 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAH27ORMOCGUXF7RDICOV32BSSGFAVCNFSM6AAAAABRSD25Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBYHA3DMNBZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER APOSTROPHECMS | apostrophecms.com | he/him/his

[milaninfy]

it does if the package you are viewing is not scoped..