3 ms·
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" t
by xirdstl 11y ago
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.
- kibwen 11y agoNew 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!