Windows Support: nested `node_modules` dirs too long for windows to handle?

[aarosil]

It appears the Project does not work on Windows (though it may be a greater issue with node)

I have Windows 7 enterprise 64bit version. I attempted to run clever init myTestApp and it did not complete for ~40 min so I Ctrl-C'ed the command

I then attempted to re-run it again, using --force to overwrite the existing app, but it failed on removing some directories.

I then opened Windows explorer to remove the directories, but it failed, saying "The source filename(s) are longer than what is supported by the system. Try moving to a location which has a shorter pathname".

Given that Windows blows, I am not sure what can be done here. I've worked around this problem with special Git options, but this isn't a git repo so I'm not sure how I'd use that to solve the problem here.

Anyway just thought I'd leave a note here about the problem in case you guys have any suggestions. I see you prominently displaying notes for "Windows Users" througout the docs, so hopefully I'm just missing something simple?

[pilsy]

What is the directory you are storing the application in?

[aarosil]

It's something like C:\Users\HOME\aarosil\Projects. Upon further reading after I posted, it seems npm team is aware and working on a solution for this.

[pilsy]

Yeah but it's been a problem for quite some time with NPM, so it's unknown when they will fix it (or rather, find a workaround for the windows limitation)

I would try putting the project in something like, C:\Projects\projectName - this is what i used to do on my windows pc - i then progressed to using running node on an ubuntu vm and editing the files over a samba share - now i use a 15" macbook pro

CleverStack does help somewhat by installing all CS module npm dependencies inside the project root directories node_modules folder (C:/Projects/projectName/node_modules) - it does this to allow the root application access to the dependency but also helps in the long windows paths