Is it just me, or should package managers not be transactional in nature? Is it true that ^c'ing "npm install" can leave your stuff broken such that another "npm install" doesn't fix it?

(So, yes, I am on Ubuntu 14.04 LTS with older npm. So, yes, updating in theory solves it, except for how that is the kind of BDUF that should go into any package manager from the get-go, is my point. It shouldn't be only in the 3.x (Win 3.1 jokes aside) version that the so-called package manager stops being fundamentally wrong headed. Oh and it is so funny how now people are using "npm@3" instead of e.g. "npm 3.x" because it is nice to add any little potential confusion to things whenever possible. You know, because we really do want to break people down with a zillion little paper cuts.)