path is too long

[infofromca]

when install it from dev or 1.9.x, 1.9.1 today's version,
got this error. (visual studio 2013)

"~/Modules/Orchard.DynamicForms/node_modules/gulp-less/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/indent-string/node_modules/repeating/node_modules/is-finite/node_modules/"

[infofromca]

http://blog.icanmakethiswork.io/2014/12/gulp-npm-long-paths-and-visual-studio-fight.html

[sebastienros]

I know it has been fixed in the latest npm version.

[bleroy]

Link?

[bleroy]

Duplicate: #5561

[Skrypt]

https://windows.uservoice.com/forums/265757-windows-feature-suggestions/suggestions/6573539-remove-the-long-standing-max-path-limitation

Vote :)

dotnet/msbuild#53

[Skrypt]

We should then automate the removal of those node_modules before publishing.
Or we could also excluse those folder from publishing.

http://blogs.msdn.com/b/webdev/archive/2010/04/22/web-deployment-excluding-files-and-folders-via-the-web-application-s-project-file.aspx

[Skrypt]

Not working either.

http://stackoverflow.com/questions/25237823/actually-excluding-files-from-publish-without-verifying-it

Though the guy seems to have a workaround by installing some (if not all) of the dependecies globally:

npm install -g package

and then installing into the project using

npm install --link

[Skrypt]

Added this in PRE build event command line of the 3 projects that holds node_modules folders.

if exist "$(ProjectDir)node_modules"  ( rimraf $(ProjectDir)node_modules )

It deletes the folders but that's not really an adequate solution. Though it fixes the publish problem automatically. You also need to install rimraf globally before :

npm install rimraf -g

[DaRosenberg]

This will be fixed as part of #5450.

[dcinzona]

Agree with @Skrypt - Installing globally isn't really a viable solution for everyone using the source. Not to mention that this would force npm to reinstall the node modules every start up and that gulp would fail after deployments.

@DanielStolt I mentioned this in the dupe issue: I had success creating a generic project and adding it to the solution, adding the gulpfile and package.json manifest to it. This allows me to download all of the npm modules into a separate directory in the root and avoid deployment issues. Just need to remember to add it to all solutions (Azure Cloud Service and Orchard.Web).

As you had mentioned before, including a .gitignore and .tfignore config in there would be beneficial as to not commit those node modules to source control.

[DaRosenberg]

@dcinzona This sounds like what I have in mind? Going to work on it this weekend.

[dcinzona]

Awesome! Looking forward to it
Thanks @DanielStolt

[DaRosenberg]

Fixed in 6da6c5c.