@types/react support for version 17 #146
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
I am getting dependency resolving issues when trying to update the version of @types/react, so I'm proposing a wider SEMVER support for this peer dependency
|
+1 for this, my CI workflows have been broken since the new version of npm is more strict about dependency resolutions. Would love to see this merge happen. |
jasongaare
approved these changes
Jun 30, 2022
Closed
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.
Hi,
I am getting dependency resolving issues when trying to update the version of @types/react, so I'm proposing a wider SEMVER support for this peer dependency.
While this issue can be easily skipped by forcing the legacy peer dependencies, I believe it will be better to just support version 17 here
Please let me know if this makes sense for you.
Thanks for this great library!