Hacker News new | ask | show | jobs
by stu2010 1682 days ago
You cannot actually do this at npmjs.org, regularly used packages can only be marked "deprecated" now: https://docs.npmjs.com/policies/unpublish
1 comments

The article mentions this, and links to the same page.
Still, though, could there not be a similar scheme where instead of unpublishing the module, the maintainer intentionally inserts a divide by zero somewhere and pushes it as a minor update?
To my mind, that crosses some invisible line, that unpublishing a module does not.
What would divide by zero do for a JS dependency?
That's how you break the web