News for hackers. Stuff that matters.
Re:Changes to Npm's unpublish policy by xirdstl on Tuesday March 29, 2016 @01:36PM (#11383196)
We also ran into this issue just last week and used the "find and replace" method.

Here's one incredibly horrible solution (hack): publish your own "package" to NPM which depends on the shrinkwrapped versions of your dependencies. Per this policy, they won't delete your dependencies since your NPM package explicitly depends on them.

Re:Changes to Npm's unpublish policy by kibwen on Tuesday March 29, 2016 @02:08PM (#11383517)
New startup idea: "Dependence As A Service". For a nominal fee we'll automatically upload a package that depends on any version of any other package that you desire, and we guarantee that we will never yield to any frantic, desperate pleas to excise these dependencies!