You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[TSC] choose a npm publication method for the future #87
In Express we are trying to do a CI version with 2FA (under discussion: expressjs/discussions#443), so we can probably adopt it if we want to avoid local publication due bus factor
My two cents: I recently enabled this for raw-body, and compared to webpack's current workflow, it only adds one extra step: logging into npm and approving the publish request with 2FA.
It really depends on who is doing the release and from where. Right now, you can merge a PR from your phone and trigger a release. With this change, you'd also need to log into npm, complete the 2FA, and approve the publish request.
Activity
evenstensberg commentedon Jul 13, 2026
status:
UlisesGascon commentedon Jul 13, 2026
Probably this will help us to decide: openjs-foundation/security-wg#339 👍
bjohansebas commentedon Jul 13, 2026
My two cents: I recently enabled this for raw-body, and compared to webpack's current workflow, it only adds one extra step: logging into npm and approving the publish request with 2FA.
It really depends on who is doing the release and from where. Right now, you can merge a PR from your phone and trigger a release. With this change, you'd also need to log into npm, complete the 2FA, and approve the publish request.
evenstensberg commentedon Aug 10, 2026
status:
we will try this on https://github.com/webpack/coffee-loader first.
evenstensberg commentedon Sep 7, 2026
Status