This is especially problematic for the global folder. See #3110 (comment)
This is at the top of my weekend priority queue. Damn, I thought we'd really gotten these things straightened out.
Actually, I'm starting to think this isn't a problem, except for legacy jitsu installs. Because after npm 1.2.10, it's impossible to install a package with invalid peer dependencies (it might work with --force?). So a user shouldn't be able to get into this situation where there's a "poisoned" folder.
It remains that there's a lot of bad jitsu installs out there, especially in the global node_modules folder, which poison global installation (see link in OP). I'm not sure there's a good solution for this though. @isaacs, thoughts?
(I came to this conclusion after writing a test that installed a bad peer deps package then installed another, but it passed immediately since the bad peer deps package never showed up in node_modules and thus never prevented installation.)
so will there be a npm repair, npm fix or npm antidote ... something like that?
I mean, you could just alias npmrepair to npm uninstall jitsu -g; npm install jitsu -g.
npm uninstall jitsu -g; npm install jitsu -g