Long path support issues on windows when using npm3
See original GitHub issueDescription
TL;DR when using npm3 node packages should not include their dependencies. ie shouldn’t have a sub node_modules folder. on windows this can cause long path names. longer than what windows can support. npm guidance https://docs.npmjs.com/how-npm-works/npm3
Long story but we use cake build scripts and it doesn’t support long files paths on windows. We have had a similar issue recently when phantomjs broken release.
Environment
npm ls react-scripts
(if you haven’t ejected): react-scripts@0.7.0node -v
: v4.4.5 / v6.9.1npm -v
: v3.7.1 / v3.10.8
Then, specify:
- Operating system: Windows 10 and Windows Server 2012
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
npm and distribution path length problems - Adam Lynch
NW.js is great for creating desktop applications using Web app technologies. ... You might see people reference Windows APIs (which support long paths)...
Read more >Node/npm MAX_PATH issues · Issue #69 · microsoft/nodejstools
The cmd line should play nice with VS, but no plans to support it through UI. ... @mousetraps with npm@3.1.1 recently released the...
Read more >Node npm windows file paths are too long to install packages
The problem with deeply nested folders on Windows has been mostly solved starting with npm version 3.x . According to npm: .npm@3 makes...
Read more >NPM vs. Windows' MAX_PATH Limitation - Scott Addie
Long path tool is the very good program for error, unlock solution. Try it and solve your problem. I used long path tool...
Read more >path too long error on windows 10 - Laracasts
when I run the npm install on windows machine after setting up laravel I get the following error: C:\Program Files (x86)\MSBuild\Microsoft.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We control bundledDependencies. We added them to cut the install time on npm 2. However now that Node 6 is the LTS release (and comes with npm 3) it may be a good time to drop support for npm 2 and remove bundledDependencies.
Bundled dependencies were removed in #1068 so this should be fixed in the upcoming release.