You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest patch version of node apparently ships with a version of npm that causes our windows-tools test to fail. (It logs deprecation warnings with every npm script run that messes up our cli test assertions). The latest npm version fixes that. npm/cli#4980
It seems easier to just pin the version of node for the windows-tools test to one that shipped with working npm and unpin later once the latest v16 of node includes that.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
The bug is that any npm script run will always spit out
`npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.`
which the test is not expecting to see.
Speaking with @justinfagnani offline, we were wondering if it's possible to pass like a --silent flag to the npm call so that the warning above gets suppressed. Or should the test assertion be written to be able to ignore other outputs?
This is also hopefully just a temporary thing so maybe it'll be fine to pin for now and unpin soon, though at the risk of any future unexpected output resurfacing this again.
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
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.
The latest patch version of node apparently ships with a version of npm that causes our windows-tools test to fail. (It logs deprecation warnings with every npm script run that messes up our cli test assertions). The latest npm version fixes that. npm/cli#4980
However, updating npm for Windows isn't as simple as
npm i -g npm@latesthttps://docs.npmjs.com/try-the-latest-stable-version-of-npm#upgrading-on-windowsIt seems easier to just pin the version of node for the windows-tools test to one that shipped with working npm and unpin later once the latest v16 of node includes that.