Should publishConfig.registry take higher priority than .npmrc config on npm publish?

[JounQin]

For example, If I have publishConfig.registry = registryA in @scope/foo's package.json, and $cwd/.npmrc with @scope:registry=registryB, when I run npm publish on @scope/foo, I'd expect to publish it to registryA instead of registryB.

However, the current behavior is unexpected to publish on registryB.

I have registryB as a proxy for registryA + official npm registry, what means it will resolve regsitryA first and try offical npm registry at the same time on installing, so that we can have some internal packages with some open sourced scoped packages at the same time.

[JounQin]

Close in favor of npm/cli#7043