[BUG] npm registry not showed on publish --dry-run

[Eomm]

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"

[ljharb]

npm 3.8.1?

[Eomm]

Yes, npm 3.8.1

This is the publish output without the dry-run:

with dry-run:

[ljharb]

@Eomm i'm confused; npm 3 is very, very ancient, and node 17 ships with npm 8. Do you mean v8.3.1?

[Eomm]

Oh sorry, I missed the typo.. twice! 😂

Let me copy-paste it:

➜ npm -v       
8.3.1