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
ERR 400 2FA when no 2fa is configured on account/repo #494
Comments
Why it is not possible to make this |
See: npm/cli#650 |
It's so that it can handle when you first publish a new package as you cannot enable 2FA on a package before it's published. Was just easier to have the same logic for both existing and new packages. |
Hey there, Recently published a new package too and encountered the same issue. Because the 2FA step fails and exits, the push to Github isn't happening. For now I'm pushing manually. Weirdly enough, I've been using np before and never had this issue, so I don't fully understand what is happening 😄 |
I just downgraded to 5.2.1 because this is broken. Let me know when it's fixed. That said, thanks for the wonderful work! |
I'm having the same issue with v6, downgrading works. |
Encountering the same issue. But downgrading to 5.2.1 works. Despite this, |
This is odd, I just had this issue but I am already using v5.2.1... What is happening? |
For now I am using @pixelastic's fork from #515, it's working perfectly for me.
|
Downgrading to Could there be something else failing too? |
@nerdyman Can you try my last suggestion just out of curiosity? |
Same problem here with 6.10.2 on OS X I'm having the same issues with a public package, for which 2fa is intentionally off. np fails with the following error (though the package is published anyway):
|
@dhowe Can you try my last suggestion just out of curiosity? |
Yes I am using that solution now -- works well, thanks |
I also had to downgrade to 5.2.1 to publish a new package because I couldn't get around this. Any chance you could just support the flag from the optional branch posted above? This is clearly a pretty big inconvenience for a lot of people. |
Thanks @papb, that solution worked for me, I used
It would be really good to get this officially resolved though, doing package releases via random tarballs makes me feel dirty. |
2020-07-18T07_38_21_727Z-debug.log This is still happening. And bug #427 references this issue as well. |
No need to downgrade or install other forks.... I have version 6.5.0 and there is support to the |
The actual https://github.com/sindresorhus/np/releases/tag/v6.4.0 I think we can close this issue! |
There is an issue with the latest version 6.0.0 of
np
after the package is published it tries to do 2fa and it fails. The account doesn't have 2fa enabled, as well as npm repo. Also, the package is published and then it tries to do 2fa, that seems strange I would expect 2fa is a step before publishing.Description
Here is the log file,
Expected behavior
I expect for the script to not try to enable 2fa as there is no configuration for it, and to finish everything up as a previous np v5.x.x
Environment
np - 6.0.0
Node.js - 12.13.x
npm - 6.12.x
Git - x.x.x
OS - WIN10
The text was updated successfully, but these errors were encountered: