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

2FA fails with 400 Bad Request on initial package publish #427

Closed
mikehardy opened this issue Jun 4, 2019 · 6 comments
Closed

2FA fails with 400 Bad Request on initial package publish #427

mikehardy opened this issue Jun 4, 2019 · 6 comments

Comments

@mikehardy
Copy link
Contributor

Description

I created a new package, got it all ready, and I go to publish it with np but on initial publish I get

✖ Command failed: npm access 2fa-required PACKAGE_NAME
npm ERR! code E400
npm ERR! 400 Bad Request - POST https://registry.npmjs.org/-/package/PACKAGE_NAME/access

Steps to reproduce

  1. mkdir MyAwesomeNPTest && cd MyAWesomeNPTest
  2. npm init then do what you need to make it a valid package for np publish, like make the test script empty so it passes...
  3. npx bin np

Expected behavior

I expect a bunch of happy output, probably ending in a rocket ship emoji ;-)

Environment

np - 5.0.2
Node.js - 12.2.0
npm - 6.9.0
Git - 2.20.1
OS - Ubuntu 19.04

@mikehardy
Copy link
Contributor Author

It is worth noting that the package did successfully publish.
The 2FA failure interrupted the process so git push --tags didn't execute and the release draft wasn't opened, but np did it's main job: get the release out, so that's useful

@itaisteinherz
Copy link
Collaborator

Note that this is quite similar to #424, and so the two issues might be caused by the same problem.

@danielbayley
Copy link

Same thing happening to me :/

@techhead
Copy link

2020-07-18T07_38_21_727Z-debug.log

This is still happening. And there are at least two bugs for this issue, this one and #494 .

@techhead
Copy link

It would be nice to have a way to continue the process when something breaks as well.

@mikehardy
Copy link
Contributor Author

Closing out old issues / personal git cleaning... - closing in pref to #494

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

4 participants