3 ms·
Remember "How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript" https://www.theregister.co.uk/2016/03/23/npm_left_pad_ch
by gus_massa 8y ago
Remember "How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript" https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/
- gitgud 8y agoTrue, but it's now no longer possible to remove a package from npm, which kind of solves this module resolution problem. However a malicious actor could still upload a broken minor version that most node projects would try to automatically resolve to, and thus break...
- dangerface 8y ago> which kind of solves this module resolution problem Your exception is not limited to malicious actors as even ligitmate packages like uglifyjs have had to do this. The NPM developers themselves have no problem deleting packages which would result in the same problems. They solved their problem by pushing it onto the rest of us.
- muzani 8y agoThe resolution of this also brings up why people dislike NPM. It's no longer about the whole open source thing anymore. What you put up there stays up there and isn't really yours anymore.