I've worked with all of these as well, and npm is probably my least favorite. Above all else, I expect my build system to do ONE THING: Exactly reproduce a bui

I've worked with all of these as well, and npm is probably my least favorite. Above all else, I expect my build system to do ONE THING: Exactly reproduce a build at a later date Part of it is technological (npm didn't have package-lock.json until very recently), part of it is organizational (the npm repository is surprisingly fluid), and part of it is cultural (the JS community likes zillions of tiny constantly-changing libraries). The net result is that I cannot walk away from a JS build for three weeks without something breaking. It breaks all the time. UGH.