Open Bug 1490802 Opened 1 year ago Updated 1 year ago
mach bootstrap fails on windows with too long path for node module
Edit: See [this comment for instructions on how to workaround this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1490802#c5). Was trying to run into to make sure I had node properly set up, but got this: WindowsError: [Error 206] The filename or extension is too long: '.\\node\\node_modules\\npm\\node_modules\\npm-profile\\node_modules\\make-fetch-happen\\node_modules\\https-proxy-agent\\node_modules\\agent-base\\node_modules\\es6-promisify\\node_modules\\es6-promise\\lib\\es6-promise\\promise' Windows 10, running mozillabuild in C:/gecko It got me far enough to get past configure, but I'm still running a clean build now to see if my build system is even coherent.
full log attached
In theory, npm the version of that we're shipping is supposed to have fixed this, so I'm not sure why we're hitting it: https://stackoverflow.com/questions/26155135/node-npm-windows-file-paths-are-too-long-to-install-packages I'm also not sure why more people haven't encountered this bug. I suspect we're going to end up using yarn rather than npm, so we may be able to workaround whatever the problem is just by removing npm from our repacks.
(In reply to Dan Mosedale (:dmose, :dmosedale) from comment #2) > I'm also not sure why more people haven't encountered this bug. I just ran into this issue, that I solved by moving the MOZBUILD_STATE_PATH folder to a different location.
Thanks for the workaround, Paolo! Having looked at one of the archives for the newest version of node 8, I suspect the version when we upgrade our version of node to 8.12.0, the version of npm included there will have much shorter paths.
You need to log in before you can comment on or make changes to this bug.