[BUG] npm registry not showed on publish --dry-run #4317
Description
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
Running:
npm publish --verbose --access restricted --dry-run
does not show the registry information added in #4143
Running the publish command without the --dry-run flag the registry is shown as expected.
Expected Behavior
The npm cli should show the registry information
Steps To Reproduce
Just run:
npm publish --verbose --access restricted --dry-run
Environment
- npm: 8.3.1 <-- edit: fix version
- Node.js: 17.4.0
- OS Name: macos
- System Model Name:
- npm config:
; "user" config from /Users/mspigolon/.npmrc
//registry.npmjs.org/:_authToken = (protected)
access = null
if-present = true
init-license = "MIT"
; "project" config from /Users/mspigolon/workspace/xxxcutxxxxx/.npmrc
@xxxcutxxxxx:registry = "https://npm.xxxcutxxxxx.net"
//npm.xxxcutxxxxx.net/:_authToken = (protected)
; node bin location = /Users/mspigolon/.nvm/versions/node/v17.4.0/bin/node
; cwd = /Users/mspigolon/workspace/xxxcutxxxxx
; HOME = /Users/mspigolon
; Run `npm config ls -l` to show all defaults.
; "publishConfig" from /Users/mspigolon/workspace/xxxcutxxxxx/package.json
; This set of config values will be used at publish-time.
registry = "https://npm.xxxcutxxxxx.net"