3 ms·
To be fair, the way that JavaScript development works these days, particularly anything involving npm, is batshit insane. I should not have 400 MB of hundreds
by thrower123 8y ago
To be fair, the way that JavaScript development works these days, particularly anything involving npm, is batshit insane. I should not have 400 MB of hundreds of thousands of tiny files sucked down into my node_modules folder for a simple web front-end, with 17 different version of lodash required by different packages, and dependencies nested so deeply that I can't even delete the directory without resorting to specialized tools. It's a complete disaster as far as being able to verify your dependencies, and we're sort of just blanket operating on the assumption that everything is always licensed with an MIT-alike license.
- farnsworth 8y ago> and dependencies nested so deeply that I can't even delete the directory without resorting to specialized tools I think this hasn't been an issue on windows for a while
- Klathmon 8y agoIt is still an issue, but it's not nearly as common any more with javascript development. npm a while back moved to a "smarter" way of deduping and laying out files in a more "flat" way to avoid the massive bloating and tons of copies of the same libraries. And other tools (like yarn) do the same (or better!). And the long paths issue is solvable, but you need to use the funky `\\?\` path prefix, or the tool you are using needs to support long paths on windows (which annoyingly explorer.exe doesn't, so you are stuck using hacky workarounds or other tools to delete or modify those files.