Allow finer-grained permissions on publish rights, using dist-tags as a discriminator
zakhenry opened this issue · comments
This is a Feature Proposal
Description
It would be ideal if there was the ability for a developer to publish pre-releases only, ie npm publish --tag pre but be denied the right to publish the stable releases. This could be configured in the form of an environment variable NONADMIN_PUBLISH_DIST_TAGS=pre,next.
This allows the workflow of a developer working with a module and publishing it to the repo under a prerelease dist tag, then using it temporarily in another repo to validate an idea (that can't just be tested entirely locally with npm link), or continue work while the first change is being reviewed.
Interesting concept, if there were enough users giving this a 👍 as a use case we can look to implement. Personally I am not sure how many developers work in this way, teams should be trusted to use dist-tags properly for this workflow I feel.