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: Yes, but we have no control over the npm package dependency graph :) For the majority of use cases, it's probably not an issue though. Just an idea, is it absolutely necessary to copy to the "obj" folder on build for NodeJS solutions? I realise there are advantages to copying this behaviour from other solution types in VS, but if it adopts more of the "Web site" project approach, then you don't have this issue as you attach directly to the root project folder. But I guess you have to factor in the pros & cons. Good luck :)
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: Yes, but we have no control over the npm package dependency graph :) For the majority of use cases, it's probably not an issue though. Just an idea, is it absolutely necessary to copy to the "obj" folder on build for NodeJS solutions? I realise there are advantages to copying this behaviour from other solution types in VS, but if it adopts more of the "Web site" project approach, then you don't have this issue as you attach directly to the root project folder. But I guess you have to factor in the pros & cons. Good luck :)