Re:Changes to Npm's unpublish policy
by btilly on Tuesday March 29, 2016 @05:58PM
(#11385261)
However this case matters because it closely resembles what got a developer pissed off enough at npm to unpublish hundreds of modules.
And the current changes don't help with the pissed off developer scenario much. Because a pissed off developer can simply publish broken versions of packages instead of unpublishing them, and still break the world.
And the current changes don't help with the pissed off developer scenario much. Because a pissed off developer can simply publish broken versions of packages instead of unpublishing them, and still break the world.