The npm community forum has been discontinued.
To discuss usage of npm, visit the GitHub Support Community.
[npm tokens] - Organization tokens
What about having token created at the organization level?
By doing this, you prevent things to break if someone leave the company and you (of the person) delete his account.
It would also be awesome if organization tokens had a permission to allow someone in the organization to publish a new package under the organization scope. Currently publishing a new package to an org requires an org admin and can’t be delegated AFAICT.
Hm. As long as the publishing user is a member of an org team (like “developers”) they should be able to publish new packages scoped to the org, regardless of whether they’re at owner, admin, or developer membership level.
awesome! thanks for the info