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
Lerna with npm 2FA (npm otp) #1137
Comments
Could someone kindly provide any updates on this issue? |
I discovered in npm doc: https://docs.npmjs.com/misc/config#environment-variables You may give a try to |
Was not able to use npm_config_otp, it does not change anything. Maybe because I am also using npmClient: yarn and yarn does not support that? |
cc @neoziro is this working for you? What's the command line you are using exactly? |
But I finally turn two factor authentication on npm to auth-only and I am very happy 👍. |
Indeed that ease the process, here's how to do it: npm profile disable-2fa
npm profile enable-2fa auth-only thx @neoziro |
Sometime I am currently using |
@rickmak true, i wrote a custom bash script for the publishing but was faced with this issue (1 otp is not enough sometimes). my solution to this was to use 2fa in |
This seems to be the same issue as #1091 except that it is less specific about how to solve the issue? |
Closing as a duplicate of #1091 |
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
After assigning 2FA on my npm account, lerna fails to publish (unless i publish once manually first for each package!)
Expected Behavior
Current Behavior
lerna publish fails if otp is added to the npm account of the publisher, there is no way through lerna to pass the
otp
.Possible Solution
pass otp to npm if otp options i passed to lerna:
Steps to Reproduce (for bugs)
lerna-debug.json
Context
Cannot publish packages anymore through lerna without going through the hassle of manually publishing each package once to add the
otp
. Or turning off the 2fa completely.Your Environment
lerna --version
npm --version
node --version
The text was updated successfully, but these errors were encountered: