[RRFC] npm publish should tell you the end point it's pushing too.

[EvanCarroll]

When I run npm publish, I'm getting

npm notice 245B  public-api.d.ts.map                                       
npm notice === Tarball Details === 
npm notice name:          @acme/angular-validators              
npm notice version:       2.16.0                                  
npm notice filename:      @acme/angular-validators-2.16.0.tgz   
npm notice package size:  11.9 kB                                 
npm notice unpacked size: 58.0 kB                                 
npm notice shasum:        7d011bd7b4a2bc58c76350713d2deb96365f9ea9
npm notice integrity:     sha512-btSJOUY06H5Un[...]VKTF44PA7g/xQ==
npm notice total files:   28                                      
npm notice 
npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-08-06T18_20_01_714Z-debug.log
Cleaning up file based variables

It would be nice to know exactly where it's pushing too, even if only behind a --verbose flag..

[juanpicado]

For context, before npm7 it was possible somehow to see the endpoint was being published npm publish -ddd

npm publish -ddd 
npm info it worked if it ends with ok
npm verb cli [
...
npm verb cli   '-ddd'
npm verb cli ]
npm info using [email protected]
npm info using [email protected]
npm verb npm-session 33df624edf18f204
npm verb publish [ '.' ]
....
npm notice total files:   3                                       
npm notice 
npm http fetch PUT 201 http://localhost:4873/npm6 354ms   <------------------------------------- registry
npm info lifecycle [email protected]~publish: [email protected]
npm info lifecycle [email protected]~postpublish: [email protected]
+ [email protected]
npm verb exit [ 0, true ]
npm timing npm Completed in 579ms
npm info ok 

[isaacs]

• Action: add registry target config output when using npm publish (should be before 2fa prompt)
• Action: should happen for --dry-run as well
• Action: consider other commands that we may want to provide this output/context (start with write operations at first)

[lukekarrys]

This was completed in npm/cli#4143.