-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[tests] rewrite doctor tests to dictate the current node version #2681
Merged
Conversation
This file contains 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
Emphasizing them like we do everywhere else to fix encoding errors and for consistency. Also removed the `<String>` from the type definition as we don't do that anywhere else. PR-URL: npm#2662 Credit: @ethomson Close: npm#2662 Reviewed-by: @wraithgar
This brought in @npmcli/installed-package-contents@1.0.7 from commit e1822cf
This pulls in, installs, and de-dupes our subdependencies. Notable updates are promise-retry and @npmcli/move-file which had new versions but we had no way to update and/or dedupe We also manually removed uuid from our package.json which was only added in the past to try to get around this same deduping issue
wraithgar
approved these changes
Feb 12, 2021
wraithgar
approved these changes
Feb 12, 2021
This decouples our tests from depending on the node version being right, and allows us to run in all of the environments we need to during CI. PR-URL: npm#2681 Credit: @ljharb Close: npm#2681 Reviewed-by: @wraithgar
wraithgar
force-pushed
the
doctor-tests
branch
from
February 12, 2021 17:20
71321c6
to
3a159d2
Compare
did you mean to update this PR so it includes 10 unrelated commits? |
No, the pull script did weird things to this PR. In the release branch though it's ok
This PR itself is just gonna look weird. |
wraithgar
added
Release 7.x
work is associated with a specific npm 7 release
release: next
These items should be addressed in the next release
labels
Feb 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
release: next
These items should be addressed in the next release
Release 7.x
work is associated with a specific npm 7 release
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.
Extracted out from #2654.