3 ms·
For years, this limitation made using npm on Windows miserable[0][1]. [0] https://github.com/nodejs/node-v0.x-archive/issues/6960 https://github.com/nodejs/nod
by rl3 10y ago
For years, this limitation made using npm on Windows miserable[0][1].
[0] https://github.com/nodejs/node-v0.x-archive/issues/6960 https://github.com/nodejs/node-v0.x-archive/issues/6960
[1] https://github.com/npm/npm/issues/3697 https://github.com/npm/npm/issues/3697
- coverband 10y agoI was just about to suggest increased adoption of nodejs on Windows is most likely what triggered this change. (I don't even use node, but if a project I'm interested in has a bunch of node modules in it, I'll have to stop and spend time to fight the path length errors.)
- coleca 10y agoNot that you should do this because it's a horrible product, but if you ever installed IBM WebSphere Portal Server on Windows, you run into all kinds of issues because of the path name length. It would install partially by unzipping into long paths and then you would be unable to uninstall it because their uninstaller would try and hit the paths directly and fail.
- jle17 10y agoAh ! Serves them right for inflicting the same problem on applications that install on AIX using the builtin tar and can't find their files after due to the path lenght limitations.
- philliphaydon 10y agoIt's not even a problem in npm 3.# because it doesn't do nesting by default anymore.
- rl3 10y agoGood point. Looks like npm 3.x emerged from beta late last year. I edited my original post accordingly, changing it to a more reminiscent tone.