Skip to content

Conversation

@alexander-schranz
Copy link
Contributor

Description

Allow usage with react 18.

Motivation and Context

Avoid: "[email protected] requires a peer of react@^16.5.0 || ^17.0.0 but none is installed"

Checklist

[x] I have not included any built dist files (us maintainers do that prior to a new release)
[-] I have added tests covering my changes
[x] All new and existing tests pass
[-] My changes required the documentation to be updated
  [ ] I have updated the documentation accordingly
  [ ] I have updated the TypeScript 1.8 type definitions accordingly
  [ ] I have updated the TypeScript 2.0+ type definitions accordingly

@jedfong
Copy link

jedfong commented Aug 2, 2022

Any estimate on when this change will be merged/published?

@hasanbisha
Copy link

it any help needed with this pr? i can give a hand

@yadomi
Copy link

yadomi commented Oct 27, 2022

Hi @arqex, could this be merged ? Also, this one #789 should probably be closed in the mean time

@arqex arqex merged commit e3bd533 into arqex:master Oct 27, 2022
@arqex
Copy link
Owner

arqex commented Oct 27, 2022

Sorry for taking so long to merge 🙏 I've just published v3.2.0 that includes the support for react 18

@pladaria
Copy link

Ok, now the same for React19

@alexander-schranz
Copy link
Contributor Author

@pladaria go for it :)

@arqex
Copy link
Owner

arqex commented Dec 12, 2024

I've just released a version 3.3.0 with react 19 as a peer dependency. I hope it works for you :)

@alexander-schranz
Copy link
Contributor Author

That was fast @arqex thx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants