> Having to explicitly call shrink-wrap is just silly. Devs on every time I've used shrink-wrap with frequently forget to do it and it causes all sorts of "works for me" problems later.
Really? An entirely new tool because you didn't like typing "npm shrinkwrap" once, just once per project? I... I don't even know how to respond to that...
> My team has also experienced all kinds of brokenness related to private NPM repositories and shrink-wrap non-determinism.
I'm unclear on what you mean? Do you mean in the past? Cause if so, sure... but hasn't this already been addressed?
> I don't care about this at all. Just because you got there first doesn't mean you should have some kind of special claim to solving the problem.
This is an all too common attitude in the JavaScript community. Hence the plethora of poorly maintained, duplicated NPM packages.
I'd rather humanity not waste the man-hours duplicating effort. Do something productive with the time you saved.
As mentioned, if for some reason the NPM guys weren't co-operative, then I understand, however that doesn't at all seem to be the case.