
Npm ERR! gyp ERR! find VS You need to install the latest version of Visual Studio Npm ERR! gyp ERR! find VS valid versions for msvs_version: Npm ERR! gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8 Npm ERR! gyp ERR! find VS looking for Visual Studio 2015 Npm ERR! gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use Npm ERR! gyp ERR! find VS unknown version "undefined" found at "D:\Program Files\Microsoft Visual Studio\2022\Community" Npm ERR! gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt Npm ERR! gyp ERR! find VS - looking for Visual Studio version 2022 Npm ERR! gyp ERR! find VS msvs_version was set from command line or npm config Npm ERR! gyp info find Python using Python version 3.9.7 found at "D:\Program Files\Python39\python.exe" Npm ERR! gyp info using ERR! gyp info using | win32 | 圆4 Npm ERR! gyp info it worked if it ends with ok Npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node-gyp rebuild

Npm ERR! path D:\heart\Git\MyVSCode\vs-shell-format\node_modules\keytar (Note that the API surface has changed to use Promises in 1.x.) Npm WARN deprecated Legacy versions of mkdirp are no longer supported. Npm WARN deprecated This package is deprecated in favor of and vscode-test. Please be aware that this package is deprecated, you should seek alternatives and avoid opening new issues about it here. Requests for help with node-sass are very common. At the least, v15 is the easiest version to get a hold of these days as it comes packaged with dotnet CLI and and the current retail release of Visual Studio.Please look thru your error log for the string gyp info using and if the version number is less than the current release of node-gyp then please upgrade using the instructions at and try your command again. My recommendation would be to have the default be the most recent stable release of the product, which I think is 15. I think that MSBuild 4.0 is also end-of-lifed (last year) so the default should at the least be MSBuild 14. Seeing as how Microsoft end-of-lifed MSBuild 2.0 and they tend to be really cautious about end-of-lifing products I think it is safe to bump the default version of MSBuild that node-gyp uses to something more modern. In order to work on any modern system users have to do something along the lines of yarn config set msvs_version 2015 -global, the npm equivalent, or set an environment variable. It is now 2017 and from what I can tell, node-gyp is still defaulting to MSBuild 2.0. NET 2.0 which was around 2005 and end-of-lifed in 2011. Someone feel free to correct me if I am wrong here but I believe MSBuild 2.0 was released with.
