fix: msvs_version is no longer a valid npm config setting
#3257
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cclauss
changed the title
msvs_version is no longer a valid npm config setting
Remove misleading warnings. % `npm config list -l | grep msvs` % `npm config set msvs_version=2025` > npm error `msvs_version` is not a valid npm option
cclauss
force-pushed
the
msvs_version-is-not-a-valid-npm-option
branch
from
725bb51 to
770ab72
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove misleading warnings.
%
npm config list -l | grep msvs# no hits%
npm config set msvs_version=2025Checklist
npm install && npm run lint && npm testpassesDescription of change