News for hackers. Stuff that matters.
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.

Re:Changes to Npm's unpublish policy by steveklabnik on Tuesday March 29, 2016 @06:15PM (#11385373)
Yeah, if I was King of npm, I would have made shrinkwrap mandatory from day 1.
Re:Changes to Npm's unpublish policy by revicon on Tuesday March 29, 2016 @11:02PM (#11386674)
This is why setting version numbers in your dependencies is important.