React 18 requirement in type definition #745
Closed
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
ghost
approved these changes
Apr 19, 2022
|
Any updates on this? I would really like to use it. |
w3bdesign
approved these changes
Apr 20, 2022
|
@w3bdesign Just noting an additional change would be needed for React 18 support which I've outlined in #741 (comment) I'm also really keen to get react 18 support merged, is there any way I can help? |
|
@ctrlplusb Would you mind taking a look? It would be great if you could fix this little type problem at the package level. Thanks |
|
Thanks ya'll. I'm busy incorporating this change. 馃憤 |
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.
With this little patch I was able to upgrade React to 18 without any additional changes in code using
easy-peasy. It might NOT fix #741 nor #740 , but it worked for me 馃槄