-
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
Visual Studio 2022 Preview - stack Error: Could not find any Visual Studio installation to use #2462
Comments
Node-sass is deprecated so we can not support it with a preview version of MSVS. |
This doesn't only happen with 'node-sass', it happens with any node-gyp module. I don't get why this is closed. |
@blattersturm Please provide the command that was typed and the full error log. |
The same portion from the error log above applies, this e.g. also happens when trying to run
Some code here hardcodes checks for 2019 when checking for MSBuild path: node-gyp/lib/find-visualstudio.js Line 272 in 782a6f1
... though the bundled node-gyp/gyp/pylib/gyp/MSVSVersion.py Line 273 in 0da2e01
Should this not fall back to pretending to be the version before if a newer one is installed? |
I believe that was fixed in gyp-next v0.10.0 https:/nodejs/gyp-next/blob/main/CHANGELOG.md |
@cclauss the issue should probably be re-opened: VS Studio: 2022 (all build tools and C++ workloads are inistalled)
Error
|
I have the same problems. When I add
And finally I found the npm was node-gyp/lib/find-visualstudio.js Lines 252 to 259 in bc47cd6
Then I tried to update node-gyp/lib/find-visualstudio.js Lines 253 to 264 in 7073c65
C:\Users\Liu.D.H\AppData\Roaming\nvm\v16.13.0\node_modules\npm on my environment. And this error disappeared.
|
I also have issues with this |
me as well |
I fixed this by downloading the 2017 Visual Studio Community on https://www.techspot.com/downloads/6278-visual-studio.html |
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: