Open jesstelford opened 6 years ago
Ahhh I didn't see this before setting up my entire repo with bolt, but now I can't publish anything since I have 2FA enabled :cry: Any workarounds?
Probably also related to #163? That would allow one to just pass the --otp
flag I think.
This workaround worked! :tada: https://github.com/lerna/lerna/issues/1091
NPM_CONFIG_OTP=123456 bolt publish
Nice find!
🤔 As mentioned in that thread; There's a situation where a long running publish (or prepublish) step can result in an expired OTP by the time it makes its way to npm.
There's currently no way to pass a OTP password to
npm
when runningbolt publish
.Looks like adding the
tty: true
option withinbolt
might allow entering a OTP on the cli whenevernpm
asks for it?These output pipelines might also have to be disabled, otherwise the terminal may get all screwy.