Quantcast
Channel: Node.js Tools for Visual Studio
Viewing all articles
Browse latest Browse all 4630

Commented Unassigned: Build fails with long filename error [862]

$
0
0
Hi,

NTVS Version: NTVS Dev 2014-03-12 VS 2013.msi
VS Version : Visual Studio 2013 Ultimate

I have a simple Express app that is using the "googleapis" package. On build, it tries to copy into the obj\Debug folder but errors with the following:

```
Error 1 Unable to copy file ".\node_modules\googleapis\node_modules\gapitoken\node_modules\jws\node_modules\tap\node_modules\runforcover\node_modules\bunker\node_modules\burrito\node_modules\uglify-js\test\unit\compress\expected\assignment.js" to "obj\Debug\.\node_modules\googleapis\node_modules\gapitoken\node_modules\jws\node_modules\tap\node_modules\runforcover\node_modules\bunker\node_modules\burrito\node_modules\uglify-js\test\unit\compress\expected\assignment.js". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Node.js Tools\Microsoft.NodejsTools.targets 74
```

Note sure how you guys will overcome this OS limitation :)
Comments: Here's another idea. On build, instead of copying the "node_modules" folder into "obj" you can perhaps just use the one from the project root. I know that there's a setting in .npmrc that can specify where the node_modules folder lives, so maybe this can be used somehow? The other option is to run "npm install" on the deployed folder eg. "obj\Debug". A bit cumbersome as this pulls down all the packages again - but you don't get the long filename issue due to file I/O from doing a straight copy.

Viewing all articles
Browse latest Browse all 4630

Trending Articles