fix: React peer dependency ranges #1893
Merged
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
ze-flo
approved these changes
Aug 19, 2024
Yeah, good call |
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.
Description
This PR gets the peer dependency ranges on
reactandreact-domdialed-in for v9. The previous>=16.8.0notation accurately includes everything since React hooks. However, some package managers incorrectly report React 18 (for example) as an invalid peer. The updated^16.8.0 || ^17.0.0 || ^18.0.0or will satisfy all package managers. More importantly, the top end of the range is capped at v18 so Garden can manage the addition of future React versions after testing.