[BUG] npm 7.x ignores publishConfig.registry

[marcusds]

Current Behavior:

npm publish does not follow publishConfig.registry, if registry is .npmrc it will try to publish to that, if not npm.org.

Expected Behavior:

npm publish publish to defined publishConfig.registry as it did in 6.x.

Steps To Reproduce:

• Install npm@latest-7
• Set publishConfig.registry IE: "publishConfig": { "registry": "https://..." }
• Run npm publish

Environment:

• OS: Windows 10
• Node: 12.18.1
• npm: 7.0.0-rc.3

[nlf]

this should be resolved! can you update to 7.0.1 with npm i -g npm@next-7 and see if it takes care of it for you?

[thw0rted]

I'm using 7.3.0 and still seeing this behavior, specifically, it fails with ENEEDAUTH immediately when I run npm publish, even though I'm logged in to the (private) repo specified in publishConfig.registry.

Reverting to 6.14.10 fixes it, as does manually specifying npm publish --registry=.... I haven't tried an earlier version of 7 (like 7.0.1) to see if it worked in October but re-broke afterwards.

[transcranial]

I can confirm this bug exists in 7.3.0.

[MikaelX]

I can confirm this bug exists in 7.4.0, and 7.4.3