Symbolic Links can be used to shorten file paths, but these are kludgy hacks. Rinse and repeat when dependencies change or when I need to spin up a new project.Fire up Cygwin and use cp to copy the node_modules folder into a destination project.
#Long path tool license install#
Run npm inside the "n" folder to install modules for whatever I need.Create an "n" folder as a staging area on the root of C:\, because.I tried the DOS2Unix transform on npm to get it working with Cygwin, but there seem to be other issues with this. Cygwin supports long file paths, but npm.cmd doesn't work out-of-box due to crlf formatting.( MS really? How long has NTFS been around?)
![long path tool license long path tool license](https://engineering.purdue.edu/ECN/Support/KB/Docs/installingnx12/2021-08-23_19-43-39.png)
![long path tool license long path tool license](https://www.xldevelopment.net/help/xldelete/toolong.jpg)
I'd like a pragmatic approach for handling this problem right now on Windows, irrespective of what the Node community may or may not provide to improve npm usability on the Windows in the future.
![long path tool license long path tool license](https://images.sftcdn.net/images/t_app-cover-m,f_auto/p/a9e0f69a-a4d4-11e6-9d8f-00163ed833e7/3828120386/long-path-tool-screenshot.jpg)
I'm hitting a wall trying to use gulp plug-ins like Browser-Sync, because the node_modules folder graph fans out making the windows file paths too long to copy the files. I want to use gulp and related front-end tool chains in Windows-hosted development environments.