feat: add --npm-browser-auth flag for WebAuthn/Passkey publish - #354
Merged
Conversation
Tony133
force-pushed
the
feat/npm-browser-auth
branch
from
July 13, 2026 13:45
486cd33 to
c565e44
Compare
Tony133
marked this pull request as ready for review
July 13, 2026 15:45
Signed-off-by: Antonio Tripodi <Tony133@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposal:
Adds a
--npm-browser-authflag as alternative to--npm-otpfor 2FA duringreleasify publish, using npm's native web-based auth flow (--auth-type=web) which supports Passkeys and hardware security keys.see issue: feat: add support for Passkeys / WebAuthn authentication #353
Usage:
Notes:
--auth-type=webtonpm publishand streams the confirmation URL live to the terminal.--npm-otpand--npm-browser-authare mutually exclusive.