5 ms·
I don't understand how NPM is such a dumpster fire. Countless other languages use package systems for a decade without constant issues. I get the feeling pure
by thermodynthrway 8y ago
I don't understand how NPM is such a dumpster fire. Countless other languages use package systems for a decade without constant issues.
I get the feeling pure JS is too dynamic for such a large codebase to be reliable. We switched to Typescript a few years back because of the same issue and I'll never look back.
All our JS/TS projects inevitably end up with rm -rf node_modules as the first build step. This has been a constant since NPM 1.X, and somehow at Node 9.0 it's still needed. I never used another package manager that was so unreliable that you need to delete all your packages just to build.
And the horrific error messages when things get messed up. I would rather debug assembly.
The regular leftpad level circus events are just icing on the cake. Please somebody replace NPM. It's even worse than the constant framework churn
- staticassertion 8y agoWhat part of this attack is npm specific? What feature of typescript would have prevented this?