Nice blanket negative statement "NPM IS BAD". Maybe you'd consider expanding on why npm frustrates you? and leaving a comment with more value.
It'd make sense to ask for such clarification if the information truly wasn't available elsewhere, and accessible with a quick search. But that's obviously not the case.
It's pointless to rehash this obvious stuff over and over and over and over again.
This one seems like a fairly reasonable candidate: http://www.jongleberry.com/why-i-hate-npm.html (though the "nested dependencies" bit needs much more swearing, and I disagree with the last paragraph suggesting things in Ruby and Python land are just as bad).
Honestly curious here.
While I don't hate npm, there are better examples of how to do package management. For example, Nuget gets a lot of things right with no nested dependencies.
I do not feel this is the proper place to go into why NPM frustrates me so much, but on a high level, I'll tell you that it has much to do with nested dependencies & lack of support for seeing more than 1 version number on their website. Bower is even worse on the latter. Look at @bshimmin's link, http://www.jongleberry.com/why-i-hate-npm.html, I share a lot of the same concerns.