> An entirely new tool because you didn't like typing "npm shrinkwrap" once, just once per project? I don't know what kind of projects you work on, but new dep

> An entirely new tool because you didn't like typing "npm shrinkwrap" once, just once per project? I don't know what kind of projects you work on, but new dependencies get added with some regularity on any large node project, requiring a shrink-wrap every time. If you've never experienced the forgetting-to-shrinkwrap problem and its interplay with team dynamics, then I envy you. But I also must give up trying to explain to you, since this drives to the heart of the problem and I must conclude that we simply do not have enough common experiences for you to ever understand. The developers of Yarn et al clearly have lived this nightmare. > Do you mean in the past Where the past was < 4 months ago. If it has been fixed since that, I don't care: too little, too late. > This is an all too common attitude in the JavaScript community. An equally big problem in the JavaScript community is that core pieces of infrastructure have been "claimed" by people who have absolutely no idea what they are doing, but are happy to community-coordinate their way to some kind of idealistic open source victory. > weren't co-operative Again, I don't care if they were willing to co-operate. I have zero confidence in them. > I'd rather humanity not waste the man-hours duplicating effort. Give up on this dream. People are going to re-invent everything from now until the end-of-time, and rightly so.