-
Notifications
You must be signed in to change notification settings - Fork 23
Support React 19 for Next 15 and React 19 upgrade in consumer apps #5552
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: b98a136 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
A bunch of tests are failing. I reckon it might be because of mismatch react version from possibly storybook? I also noticed react and react dom as dependency in the root package.json - are they needed there? |
79c5067
to
6303faf
Compare
7dd6d47
to
7a6805f
Compare
* chore: Ignore peerDep warnings for older packages Target specific packages so as not to ignore valid warnings we can ignore * chore: add react popper * chore: add popper core * chore: add changeset and order packages
Important: Request PR reviews on Slack
Please reach out to the design system team on Slack in
#prod_design_system
for PR reviews. GitHub notifications (e.g. from tagging a person) are not actively monitored.Why
To prepare for our Nextjs 15 and React 19 upgrade, I created this PR to test it out. My findings has been documented here
What