-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[windows] node-gyp fails to find Visual Studio Build Tools 2017 #2002
Comments
gyp ERR! find VS ************************************************************** |
The problem is, I have installed build tools both ways as described in https://github.com/nodejs/node-gyp#on-windows, have Python installed. Added both build tools and Python to Path and npm config variables. Still getting the same error message. :/ |
So,how did you solve it in the end. |
We are having this exact same problem on automated test machines in production. Out of nowhere all of our Windows machines are slowly failing to install/compile anything with node-gyp. I've tried re-installing windows-build-tools, both 5.2.2 and the latest v4. We're on Windows 10, NPM 6.13.4, and node 10.18.1. |
Check if changing line 270 in return path.join(info.path, 'MSBuild', '15.0', 'Bin', 'MSBuild.exe') to return path.join(info.path, 'MSBuild', '15.0', 'Bin', 'amd64', 'MSBuild.exe') will help you. |
I have this exact same problem. I am completely stuck. I've installed Python manually. I've run |
I too am having this problem. It appears to not be finding the 2015 or 2017 tools I have installed. The culprit here is node-sass which is set to node-gyp 3.8
|
Please try the solution that worked at #2069 (comment) |
@cclauss Thank you for the reply. I have removed and reinstalled the node_modules directory multiple times this morning - been fighting this for hours. node-gyp is at 6.1 in the node_modules directory. However, the node-sass compile is somehow still getting v3.8.0. I just removed the directory, verified what version of node-gyp was in the package.json and it is 6.1. Verified what installed. I still have the exact same error as above. |
node-sass has pinned itself to an old version of node-gyp: https://github.com/sass/node-sass/blob/b54053a1b50fd97e951eb0311a7fb818683a8e99/package.json#L67 |
@richardlau That's what I thought I was seeing. Thank you. I'm still a newbie at reviewing the package.json files. Ok so it sounds like I am on the wrong tree here as far as getting this to work. I need to figure out how to get node-gyp to look at VS2017 or VS2015. Thanks for the assist. |
Unfortunately neither of these seems to fix the problem. It's still reaching out to 2019 to do the compile. |
Hey @nhustak ,
says it will try to execute 32-bit binary. But the args
say that target is x64. What you need is to make it execute 64-bit binary, which is located under "amd64" subfolder. Please, read the comment above #2002 (comment) . It works for me (drawback is that it is a local change) |
@intrueder Well thank you very very much. That worked! |
WARNING: THIS MAY NOT BE SAFE FOR ALL USE CASES |
I'm going to close this. It's been inactive for over a month and it doesn't really seem to be an issue with (a recent version of) node-gyp. |
I was having a similar problem to this where After much debugging it turned out I was spawning the |
I have latest Windows 10. tried with node_gyp version 8.1.. I tried with both Visual Studion 2017 and 2019 . Still not able to proceed |
No log makes it a guessing game. |
Hi,
node-gyp fails to find Visual Studio Build Tools 2017
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: