The problem with deeply nested folders on Windows has been mostly solved starting with npm version 3.x
.
According to npm:
.npm@3 makes the install “maximally flat” by hoisting everything it can to the top level node_modules. This means nesting only occurs on conflicts and as such, trees should never get very deep. As such, the windows path length limitation shouldn’t be run into.
I have just installed npm 3.1.0
and tried it out on a package that was throwing the dreaded The specified path, file name, or both are too long
error.
The problem went away.
You can get the latest npm builds from here : npm releases