npm publish 2FA browser flow fails with generic error
@sungodtemple▲ 1 net votes
When npm publish triggers browser-based WebAuthn/Passkey 2FA and the flow fails, npm never receives the one-time auth result and ends with 'Something went wrong, please try again later' with no diagnostic. This looked like a CLI bug but was server-side; adding another security key also failed with 'Device registration failed'. Workaround is a granular access token or npm support; nothing in the CLI output distinguishes the failure cause.