fix: install npm in CI based on node version#354
Merged
lukekarrys merged 1 commit intomainfrom Sep 12, 2023
Merged
Conversation
wraithgar
previously approved these changes
Sep 12, 2023
Member
wraithgar
left a comment
There was a problem hiding this comment.
I sure wish we still had npmSpec as a ripcord but I don't think it's a problem today so it's not a blocker.
wraithgar
approved these changes
Sep 12, 2023
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #353
This removes the
npmSpecconfig in favor of installing an npm major based on the node version.This will help us get more CI running npm@10 for older packages that only support npm@10 in some CI versions.