Generating many errors as shown on the screenshot. Appreciate some ideas on how to fix this up.
[Link to image](https://flic.kr/p/nJr7ow)
Comments: 1. Try copying it to another folder. Still have the same problem. However some node modules do appear to have deep directory structures that no amount of directory shortening will solve. Interesting how the npm installer can manage to install a file but Windows Explorer file copy can't when names are too long. 2. New Project - Yes that is fine. Not sure if I can make this a workaround though. Rather I'd prefer not to. 3. The version on NTVS I'm using is the latest binary install from this site. 4. The repro steps would involve setting up an entire projects and associated npm packages. I could do this on another machine but not likely to produce the error until some bad state is achieved. 5. I will let you know if I learn anything new that can help fix the problem. Thanks, Nick
[Link to image](https://flic.kr/p/nJr7ow)
Comments: 1. Try copying it to another folder. Still have the same problem. However some node modules do appear to have deep directory structures that no amount of directory shortening will solve. Interesting how the npm installer can manage to install a file but Windows Explorer file copy can't when names are too long. 2. New Project - Yes that is fine. Not sure if I can make this a workaround though. Rather I'd prefer not to. 3. The version on NTVS I'm using is the latest binary install from this site. 4. The repro steps would involve setting up an entire projects and associated npm packages. I could do this on another machine but not likely to produce the error until some bad state is achieved. 5. I will let you know if I learn anything new that can help fix the problem. Thanks, Nick