4 ms·
It was an npm issue, fixed in npm 3. http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really-big-deal-for-windows/ http://www.felixrieseberg.com/npm-v3-is
by sonnyp 11y ago
It was an npm issue, fixed in npm 3.
http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really-big-deal-for-windows/ http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really...
- userbinator 11y agoI may be somewhat biased because my primary platform is Windows, but IMHO 260 bytes is plenty for a full path. I've personally never run into that limit with what I do, but I'm aware that there are some programming languages and environments which even encourage very deep nesting (often with directories that contain nothing more than another one), making it much harder to navigate the resulting structure. It's good to see the Node.js people recognise this situation and go back to flatter hierarchies, even if it was Windows' path length limitations that motivated it. http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ http://blog.codinghorror.com/filesystem-paths-how-long-is-to...
- deleted 11y ago[deleted]
- netcraft 11y agoThe new babel 6 stuff was the first time I had hit the limitation, but their names are extraordinarily long.
- detaro 11y agoThe annoying thing is that the limitation only exists in some APIs. So you can create paths that are to long, but then most software can't deal with them, which is worse than not allowing long paths at all.