-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React 19 compatibility #818
Comments
@leefreemanxyz Thanks for working on this, as it impacting our team! 🙇♂️ |
Any news on this? |
Hi, we are working on supporting React 19 for auth0-react and will be making a release shortly. Please note that we want this to go as smoothly as possible while avoiding any compatibility and security issues hence the delay. |
@tusharpandey13 Any update on this? |
I'm also curious if there's an update on this. I have a React 19 app I need wrapped through auth0 and am at a bit of a standstill. I may roll back to React 18, but that's obviously not ideal. |
@tusharpandey13 it looks like there were some remaining CI issues on #828 and the release never got cut. When do you think these issues might be resolved? We've been blocked from updating to React 19 for over a month at this point. |
Hi, the minor release is out v2.3.0 and a respective gh-packages release has also been made, closing this. |
Checklist
Describe the problem you'd like to have solved
Installing React 19 with npm fails the peer dependency check because this library's peerDependency range does not include React 19.
Describe the ideal solution
This library is updated to use React 19.
Alternatives and current workarounds
It is possible to continue using the --legacy-peer-deps flag but this isn't a desirable long-term solution as it can result in a 'broken' dependency tree.
Additional context
No response
The text was updated successfully, but these errors were encountered: