-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Chore/update to react 19 #7548
base: dev
Are you sure you want to change the base?
Chore/update to react 19 #7548
Conversation
ee2652f
to
6383620
Compare
What needs to be done for this to go out of draft. |
"@types/jest": "^29.5.0", | ||
"@types/node": "^20.5.1", | ||
"@types/react": "^18.2.13", | ||
"@types/react-dom": "^18.2.6", | ||
"@types/react": "^19.0.01", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"@types/react": "^19.0.01", | |
"@types/react": "^19.0.10", |
@arjenbloemsma we would also like to upgrade our stack to React 19 and we are stuck because of this. Are you ok accepting the suggestion so that we include this in the next release? |
Similar to others here, our path to React 19 is blocked due to this package. @arjenbloemsma Is this okay to be marked as ready? Is there anything we can do to assist? |
Please note that this is a "copy" of PR #7467 which got accidentally closed while doing an update to resolve conflicts
React 19 stable has been released on December 5th (see announcement). This PR updates the react packages to version 19 and also sets the peerDependecies to reflect this.
This change will allow msal-react to be used in projects that use react 19 and enables existing projects that use react and msal-react to upgrade to react 19.
All test succeed:
See issue #7455