nodejs / nodejs/node-gyp

gyp ERR! find VS - does not match this Visual Studio Command Prompt

Open
#2,819 33 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

node-pre-gyp < v2 Visual Studio not found Windows
Dominant language
Python
Stars
10.7k
Forks
1.9k
Avg merge
1d 4h
Merged PRs (30d)
5

Description

  • Node Version: v18.15.0
  • Platform: Windows 11
  • Compiler: 2022
  • Module: node-gyp
gyp info it worked if it ends with ok
gyp info using node-gyp@9.3.1
gyp info using node@18.15.0 | win32 | x64
gyp info find Python using Python version 3.11.2 found at \"C:\\Users\\User\\AppData\\Local\\Programs\\Python\\Python311\\python.exe\"
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS running in VS Command Prompt, installation path is:
gyp ERR! find VS \"C:\\Program Files\\Microsoft Visual Studio\\2022\"
gyp ERR! find VS - will only use this version
gyp ERR! find VS checking VS2022 (17.5.33502.453) found at:
gyp ERR! find VS \"C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\"
gyp ERR! find VS - found \"Visual Studio C++ core features\"
gyp ERR! find VS - found VC++ toolset: v143
gyp ERR! find VS - found Windows SDK: 10.0.22000.0
gyp ERR! find VS - does not match this Visual Studio Command Prompt
gyp ERR! find VS checking VS2017 (15.9.33423.255) found at:
gyp ERR! find VS \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\"
gyp ERR! find VS - found \"Visual Studio C++ core features\"
gyp ERR! find VS - found VC++ toolset: v141
gyp ERR! find VS - found Windows SDK: 10.0.17763.0
gyp ERR! find VS - does not match this Visual Studio Command Prompt
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8

node-gyp: 9.3.1

npm version
{
npm: '9.6.2',
node: '18.15.0',
v8: '10.2.154.26-node.25',
uv: '1.44.2',
zlib: '1.2.13',
brotli: '1.0.9',
ares: '1.18.1',
modules: '108',
nghttp2: '1.51.0',
napi: '8',
llhttp: '6.0.10',
uvwasi: '0.0.15',
acorn: '8.8.2',
simdutf: '3.1.0',
undici: '5.20.0',
openssl: '3.0.8+quic',
cldr: '42.0',
icu: '72.1',
tz: '2022g',
unicode: '15.0',
ngtcp2: '0.8.1',
nghttp3: '0.7.0'
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no repository file or test entry point. Start by reproducing the Windows 11 failure with Node 18.15.0, node-gyp 9.3.1, Python 3.11.2, and Visual Studio 2022, then trace Visual Studio detection from the logged command-prompt mismatch. Done means the mismatch is explained or corrected and covered by a reproducible verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, python
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.