TL;DR

Use the Visual Studio Installer to get the Desktop development with C++ workload in one of the Visual Studio versions you have installed in your machine:

2024 update: also "check the Windows 10 SDK in the installation details" (thanks Nicholas)

Reason/Details

Reading through the log, the main error is due to this:

msvs_version not set from command line or npm config

After this one you find a few of these:

"Visual Studio C++ core features" missing

And later:

You need to install the latest version of Visual Studio including the "Desktop development with C++" workload.

For more information consult the documentation at:

VS https://github.com/nodejs/node-gyp#on-windows

Finally:

Could not find any Visual Studio installation to use

So to solve the problem, you just need to get "Desktop development with C++" workload.

If you have a Visual Studio version installed

1. open Visual Studio Installer (Win + search for it)
2. on the list displayed with all Visual Studio Installations you have in your PC, press the Modify button of one of them (preferably the latest version)
3. on the Workloads grid/list select the checkbox with Desktop development with C++ (2024 update: also "check the Windows 10 SDK in the installation details" (thanks Nicholas))
4. Press one of the Install buttons

gyp will then find that version and use it:

gyp info find Python using Python version 3.8.1 found at "C:\Users\USER\AppData\Local\Programs\Python\Python38-32\python.exe"

gyp info find VS using VS2019 (16.4.29709.97) found at:

gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\

With NO Visual Studio installed

The following solutions assume you have node installed. Disclaimer: I did not test any of them, but I appreciate everyone that reported them solving this issue.

Alternative 0: before installing additional software

As kaulshapranav wrote in a couple of comments, slightly shortened/rephrased:

windows-build-tools installation log mentions this tools package is deprecated and is already included with node. It corrupts my anaconda installation by installing a separate python 2.7 (...); updating npm version from 6 -> 8 solved the issue.

npm comes with node, so the solution: update your node/npm version. However, if you need to retain specific versions, nvm (notice the v) allows to change between them: simple tutorial on how to use nvm.

Alternative 1

As Hamid Jolany's answer suggests, on an admin shell, simply install the build tools package globally (node-gyp README):

npm i -g windows-build-tools 

Alternative 2

Ragavan's idea/answer from a similar thread:

1. verify if you have VS build tools by running npm config get msvs_version (if you have, skip to step 4 and attempt setting the environment variables)
2. if not installed, get the VS build tools latest version exe and install it (Ragavan's idea was with or Microsoft Build Tools 2015)
3. run npm config set msvs_version 2019 --global (or npm config set msvs_version 2015 --global according to Ragavan's idea)
4. Possibly optional: set the VCTargetsPathenvironment variable (Win + search for var) to the appropriate path (e.g. C:\Program Files (x86)\MSBuild\Microsoft\Portable\v5.0) or through Run as Admin terminal, as in Ragavan's idea with the 2015 Build Tools:
   • set VCTargetsPath="C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140"
   • or in Powershell: $env:VCTargetsPath=C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140

Side notes:

• a previous error might be resolved by installing Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019;
• you might also want to restart after installing any of the above

Install all the required tools and configurations using Microsoft's windows-build-tools using npm install --global windows-build-tools from an elevated PowerShell or CMD.exe (run as Administrator).

Full Guidance in GitHub

To get this to work with Visual Studio 2022, I had to run:

npm config set msbuild_path "C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin\MSBuild.exe" 

I solved the issue with npm install -g node-gyp, then npm install.

I finally solved it on my end here is how I did it

1. run this command on visual studio: npm config get msvs_version( mine was saying undefined)
2. then I run npm config set msvs_version 2022 --global(I was not seeing undefined anymore)
3. Then run: npm install. then I run my automation but this time I was seeing (Miscellaneous Warning SELF_SIGNED_CERT_IN_CHAIN:)
4. then I run set NODE_TLS_REJECT_UNAUTHORIZED=0 and voila!!! it is working

I hope this helps .it was really annoying because some of my automation file was not working

Use the following command before npm install:

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

Changing \Enterprise\ to \Community\ worked for me.

I wanted to give a recent update. After dealing with this problem for some time, it has become pretty clear to me that some versions of node (currently using 14.19.1) are not able to properly detect build tools for Visual Studio 2022. However, they have no problem detecting build tools for Visual Studio 2019. I was able to get everything working by having Visual Studio 2019 installed alongside Visual Studio 2022. First, you have to undo all the fixing you've been trying to do:

npm config delete msvs_version npm config delete msvs_version --global npm config delete msbuild_path npm config delete msbuild_path --global 

Then, download Visual Studio 2019 Community, and during install you must select "Desktop development with C++". At this point, when running npm install, node-gyp will still find your Visual Studio 2022 installation directory and attempt to use it (even if you set msvs_version to 2019), so you must add VCINSTALLDIR into your User environment variables (Start, System Properties, Environment Variables) using this directory:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC 

After this, run "refreshenv" at the command prompt, then run npm install, and feel refreshed that the suffering is over. These kind of problems are very unfortunate for us programmers. Hope this works for you.

Visual Studio Installer -> Modify Installed(Visual Studio Community 2019) -> Workloads(tab) -> [x] Desktop development with C++ -> Install

Start by running this (you can edit the year and type of VS you have i.e 2022 and community)

npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe"

Afterwards Run npm install -g node-gyp, then npm install.

Make sure all this is done within the project.

Try

npm install --global --production windows-build-tools --vs2015 

It worked for me.

A nice alternative it is to reinstall nodejs add ensure that the checkbox in "Tools for Native modules" step it is CHECKED. This is very important because it will install all the things needed to run apps in this kind of scenarios. I have face the same issue and this solve it.

After the nodejs installation will start the installation the other tools in power shell, in my case in a few moments the process stops but restart with only pression enter. After a few minutes all was done

I tried to solve this issue using npm i -g windows-build-tools but not working then I install Visual Studio Build Tools desktop development with c++ tools and finally successfully solved this issue

My solution was combination of all previous fixes:

1. Install Visual Studio 2017 (https://my.visualstudio.com/Downloads?q=Visual%20Studio%202017 - It will ask you to log in, choose Build Tools for Visual Studio 2017 (version 15.9))

   When installing, choose Desktop development with C++ (or similar name)

2. In C:\Users\<your_username>\ open .npmrc file and delete everything inside, save and close file

3. Now you need to set environment variables. If you don't know how to do it google it.

   3.1 In section user variables click new, set variable name as VCINSTALLDIR and variable value as C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\ (note that path can be different in your case but make sure that VC path is provided).

4. In terminal do:

   4.1 npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe" (note that location can be different in your case, but make sure you are specifying correct path to MSBuild.exe including MSBuild.exe)

   4.2 npm config set msvs_version 2017

5. Now you can run build or install. When I did all the steps, I didn't get error.

I only installed C++ build tools (refer picture) through Visual Studio Build Tools (2019 version). No other steps required for me on Win 10 Pro.

I got the same issue and was confused about what I should do. I searched the whole web and still no solution. What I decided to do is that

npm outdated 

When you try this command you will see all the versions basically and in detail you understand which version is needed, which is the latest version at that moment, and which version your project json file has.

C:\GitHub\portfolio>npm outdated Package Current Wanted Latest Location Depended by babel-plugin-styled-components 1.13.3 1.13.3 2.0.7 node_modules/babel-plugin-styled-components portfolio babel-preset-gatsby 1.14.0 1.14.0 2.21.0 node_modules/babel-preset-gatsby portfolio eslint 7.32.0 7.32.0 8.22.0 node_modules/eslint portfolio gatsby 3.14.6 3.14.6 4.21.1 node_modules/gatsby portfolio gatsby-plugin-google-analytics 3.14.0 3.14.0 4.21.0 node_modules/gatsby-plugin-google-analytics portfolio gatsby-plugin-image 1.14.2 1.14.2 2.21.0 node_modules/gatsby-plugin-image portfolio gatsby-plugin-netlify 2.11.1 2.11.1 5.0.1 node_modules/gatsby-plugin-netlify portfolio gatsby-plugin-offline 3.10.2 3.10.2 5.21.0 node_modules/gatsby-plugin-offline portfolio gatsby-plugin-react-helmet 3.10.0 3.10.0 5.21.0 node_modules/gatsby-plugin-react-helmet portfolio gatsby-plugin-sitemap 2.12.0 2.12.0 5.21.0 node_modules/gatsby-plugin-sitemap portfolio gatsby-plugin-styled-components 3.10.0 3.10.0 5.21.0 node_modules/gatsby-plugin-styled-components portfolio gatsby-remark-prismjs 3.13.0 3.13.0 6.21.0 node_modules/gatsby-remark-prismjs portfolio gatsby-transformer-remark 4.11.0 4.11.0 5.21.0 node_modules/gatsby-transformer-remark portfolio husky 6.0.0 6.0.0 8.0.1 node_modules/husky portfolio lint-staged 10.5.4 10.5.4 13.0.3 node_modules/lint-staged portfolio react 17.0.2 17.0.2 18.2.0 node_modules/react portfolio react-dom 17.0.2 17.0.2 18.2.0 node_modules/react-dom portfolio

Then after I figure out all reds to yellow, all the packages are installed and ready to use.

Now try it again.

Worked for me; it should work for you too.

I have had that problem with [email protected] on Windows 10 with Visual Studio 2022.

I think v7.1.2 might be not able to work with Visual Studio 2019/2022 properly.

Just try this: find a module in dependencies which uses [email protected] - for me it was gl, for you seems like sqlite3

and add an override below into the main package.json

"overrides": { "sqlite3": { "node-gyp": "9.3.1" } } 

remove node_modules and try npm install again. Hope it helps.

just update module gulp-sass to the latest version, add sass module to the package.json and write

const sass = require('gulp-sass')(require('sass')); 

to the gulpfile.js to get rid off node-gyp.

i fixed by install vscode 2017 and Desktop development with C++(im install with default optinal select download. not sure if not select default optinal see image. will error or not) with vsInstaller and set (please set with Developer Command Prompt for VS 2017) use command with your directory project not global example: cd "G:\work\projectA"

1. set msbuild_path by command: npm config set msbuild_path "G:\vs 2017\MSBuild\15.0\Bin\MSBuild.exe" (im setup with drive G by initiate because my c drive is full)
2. set msvs_version by command: npm config set msvs_version 2017 (before im use 2015 can't work)
3. im check node-gyp can work? by command node-gyp configure if not err. congat you can use npm install now

note: you can check local value by npm config get ....

If all of above doesn't help, verify that your command prompt is not customized

E.g., if you're using MS Windows and you use doskey to add aliases on startup. The tools that look for Visual Studio installation get mixed up if this happens.

You can test if this is the case by manually opening a new command prompt and verifying it has bare minimum output, such as

Microsoft Windows ... (c) ...

$Path>

For me worked the trick of using of npm 14.14.0 gyp started to work perfectly well

ps for my project I also installed Visual Studio Build Tools (2022 version) with Desktop development with C++ workload and Python311 with configuring its PATH in win10

I had got this issue after deciding to re-install node.js (update to latest version). I'm on Windows 11 and was installing node.js 18.16.1 (LTS). There is a checkbox that needs to be selected, to install the additional tools, which I've done. This in turns runs a PowerShell script that will install all that is required. For myself the script finished rally quickly, saying that nothing was done -- I thought that I must have all that's needed since I had Node installed previously. The problem actually was that it was using chocolatey to install it, and as it was already present under: C:\ProgramData\chocolatey it was skipping the whole thing.

You need to remove the entire folder - C:\ProgramData\chocolatey and run the node.js installer once more. Then the script will take quite a long time and might seem to be stuck (you can monitor the resource manager -- either CPU, disk or WiFi will be busy)

I have also had some config in the .npmrc file, which I've added as suggested by some answers on here. You can run npm config edit and remove those values -- for myself the file was all commented out then.

Additionally you need to have Python 3.10 on the Path -- it (currently) doesn't work with 3.11 (however this was giving a different error at later stage).

I had the same problem and spent hours trying to fix this. For me, the problem was the version of node used. The node I used had an internal version of node-gyp that was very old (version 5.1.0) and is NOT compatible with Visual Studio 2022. There are two ways to resolve this:

1. Use a more advanced version of node (I tried node 16.0.0 and above and they all worked for me). Versions 14.17.5 and below didn't work for me.
2. If you can't upgrade your version of node due to dependency issues, then updating your node-gyp globally won't work and you must update it internally within the location where you node version is installed. It is not complicated. Follow the instructions here: https://github.com/nodejs/node-gyp/blob/main/docs/Updating-npm-bundled-node-gyp.md Note: Using the instructions in this link - I tried installing the latest version of node-gyp and it caused new problems. So I tried using node-gyp version 9.0.0 and that worked for me.

Using

npm config set msvs_version=2022 --global npm ERR! `msvs_version` is not a valid npm option 

with space or with = errored for me.

However, npm config edit adding msvs_version={version} in the file directly worked fine.

npm config get msvs_version 2022 

Update for 2024, sqlite3 lists node-gyp:8 in its dependencies. Windows 11 SDK was added in 9. You need to install Windows 10 SDK even if you have 11.

I was able to fix this exact issue with this choco command

choco install python --version=3.10.0 choco install microsoft-build-tools --version 12.0.21005.20140416 choco install visualstudio2017community choco install visualstudio2017-workload-nativedesktop choco install nodejs.install --version=14.21.2 

If you re using NodeJS version 14.X, you should go with Visual Studio 2017.

Here my working config npm to rebuild node-gyp on:

Node version: v20.17.0 npm version: 10.8.2 Local ESLint version: ^9.11.1 Global ESLint version: not installed Operating System: Windows 10 

Open .npmrc (my location in C:\Users\HP\.npmrc)

//registry.npmjs.org/:_authToken=npm_YOUR_NPM_TOKEN msvs_version=2022 python=D:\bin\python\main\python.exe msbuild_path=C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe 

• Download Visual Studio Installer 2022
• Install Workloads Modules

Tested 01 October 2024 to rebuild node-sass, sharp, electron, puppeteer, selenium-webdriver, prebuildify.

To fix missing VCINSTALLDIR

Open environment manager, set:

VCINSTALLDIR=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\ VSINSTALLDIR=C:\Program Files\Microsoft Visual Studio\2022\Community\ 

Using npm config set msvs_version {version} errored for me as well.

However, using npm config edit then adding msvs_version={version} in the file directly worked fine.

Creds @djak250

Downgrade from version 18 to version 16.. it worked for me.