4 ms·
It 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
by Klathmon 8y ago
It 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.