Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
EvanCarroll opened this issue Aug 6, 2021 · 3 comments
Closed

Comments

@EvanCarroll
Copy link

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
Copy link

juanpicado commented Aug 6, 2021

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 npm@6.14.14
npm info using node@v14.17.4
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 npm6@1.0.16~publish: npm6@1.0.16
npm info lifecycle npm6@1.0.16~postpublish: npm6@1.0.16
+ npm6@1.0.16
npm verb exit [ 0, true ]
npm timing npm Completed in 579ms
npm info ok 

@darcyclarke darcyclarke added the Agenda will be discussed at the Open RFC call label Aug 11, 2021
@isaacs
Copy link
Contributor

isaacs commented Aug 11, 2021

  • 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)

@isaacs isaacs removed the Agenda will be discussed at the Open RFC call label Aug 11, 2021
@lukekarrys
Copy link
Contributor

This was completed in npm/cli#4143.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants