Visual Studio 2019 Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\15.0\Bin\MSBuild.exe ENOENT

[saper]

Does anyone have a workaround for this? When I run yarn and it tries to compile node-sass, it throws an error. I know this is due to the deprecated node-gyp trying to use VS2019 to compile. I've installed the windows build tools for VS2017 and VS2015 but how do I get it to look there?

gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
gyp ERR! stack     at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:80:21)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\ProjAngular\\SupervisionServices\\node_modules\\devextreme-cli\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\ProjAngular\SupervisionServices\node_modules\devextreme-cli\node_modules\node-sass
gyp ERR! node -v v12.13.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in `node-gyp`.

Originally posted by @nhustak in #2851 (comment)

[yuri-karadzhov]

I'm using sass instead it is the only reliable way for VSCode as it prebuilds packages and do not recompile them as you're changing node version.

[jvretamero]

@saper, I was facing a similar problem right now. I saw that node-sass try to download a pre-compiled binary from Github respecting the supported node version.

In my case, I was trying to install node-sass@4.9.3 (which supports node version 10) and my node version is 12. What I did was to manually download the .node file from the latest release (which supports my node version) and put it at npm-cache\node-sass\4.9.3.

After this I was able to npm install without problems. But I think that downgrading your node could solve this problem as well.

[saper]

Thanks @jvretamero - in your case you need to figure out which part of your project keeps node-sass version low (for example by requiring ^4.9). Sometimes one has to find the project and ask them to update the dependency, like I did here for Pinafore:

nolanlawson/pinafore#1625

If there is no matching binary, your system will fall back into compilation - and it might run into this issue we have here.

[nhustak]

This is has been going on for months. Apparently it's never going to be fixed. Node-Sass is locked to a super old version of node-gyp. I'm trying to figure out how to remove node-sass from my Angular build - I'll never use it again.

[joaocgreis]

As things currently stand, this workaround might work: nodejs/node-gyp#1753 (comment) . Or it might not, it's completely unsupported.

@saper please consider removing the requirement for an explicit version of node-gyp. If I understand correctly, the problem with using new versions of node-gyp is that support for Node.js < 6 was dropped. Anyone willing to use an ancient version of Node.js with known vulnerabilities should also be willing to use an old version of node-sass, and versions of Node.js < 10 should not be recommended anywhere. There are frequent issues on the node-gyp issue tracker about this (example), but nothing can be done there since new versions already fix the problem.

[CrimsonFlameDev]

As things currently stand, this workaround might work: nodejs/node-gyp#1753 (comment) . Or it might not, it's completely unsupported.

It worked for me to get around the node-gyp build errors re: MSBuild. Used the following npm config to get a good build with VS2019 Pro installed locally.

npm config set msvs_version 2017
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe"

[liudonghua123]

I have the similar issue, I got the following errors.

gyp verb command build []
gyp verb download using dist-url https://npm.taobao.org/dist
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir C:\Users\Liu.D.H\.node-gyp\14.8.0
gyp verb found first Solution file build/binding.sln
gyp verb using MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn args [
gyp info spawn args   'build/binding.sln',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=x64'
gyp info spawn args ]
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
gyp ERR! stack     at onErrorNT (internal/child_process.js:468:16)
gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:80:21)
gyp ERR! System Windows_NT 10.0.19041
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\code\\graphql\\vue-graphql-node\\client\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd D:\code\graphql\vue-graphql-node\client\node_modules\node-sass
gyp ERR! node -v v14.8.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     <https://github.com/nodejs/node-gyp/issues>

In my computer, The path C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe does not exist, the correct path for it is C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe.

Maybe an update of node-gyp could fix this path issue.

[josteink]

When installing Visual Studio 2017 C++ Build Tools v141 using Visual Studio Installer, I was able to make this install, even when running latest Visual Studio, with no additional configuration required.

[kunalverma94]

As things currently stand, this workaround might work: nodejs/node-gyp#1753 (comment) . Or it might not, it's completely unsupported.

It worked for me to get around the node-gyp build errors re: MSBuild. Used the following npm config to get a good build with VS2019 Pro installed locally.

npm config set msvs_version 2017
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe"

You Sir , Are a goooooood man ,You saved me afte i wasted 6+hours to fix this issue,I wish i had found your post earlier