-
Notifications
You must be signed in to change notification settings - Fork 243
Bump react, react-dom versions to 19.1.0, bump mui to 5.16.12 #3008
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
Open
priolette
wants to merge
2
commits into
frzyc:master
Choose a base branch
from
priolette:react-version-bump
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
💡 Verification agent
🧩 Analysis chain
Ugh, 3 AM brain talking here: Next.js 14.2.5 and a pile of other libs in this repo are still peer-pinned to React 18. Dropping in
"react": "19.1.0"
and matching@types/*
looks nice in the gacha banner, but expect red screens instead of sparkle animations:•
next@14
officially peers on^18.2
– no React 19 support yet.•
@testing-library/[email protected]
, MUI 5,[email protected]
, etc. haven’t published 19-ready versions.=> Runtime or type‐level mismatches, install warnings, maybe outright build failure.
Before merging, either:
Run a quick sanity scan:
Expect non-zero hits for
18.x
ranges – those will need attention.Also applies to: 47-48
🏁 Script executed:
Length of output: 394
I’m running on fumes here, but let’s double-check which versions of Next.js, MUI, Testing Library and React Router we’ve pinned:
🏁 Script executed:
Length of output: 485
Ugh, can’t tell if I’m hallucinating or just delirious—let’s peek at the actual peer-ranges on npm before we pull the lever:
🏁 Script executed:
Length of output: 1167
Ugh, running on empty here—Next.js and MUI aren’t ready for React 19, so you’ll hit red screens:
• package.json “next”: “14.2.5” peers on
react@^18.2.0
(no 19 support)• package.json “@mui/material”: “^5.16.6” peers on
react@^17.0.0 || ^18.0.0
• package.json “react”: “19.1.0” & “react-dom”: “19.1.0” (current bump)
• @testing-library/[email protected] peers on
^18.0.0 || ^19.0.0
(✅)• [email protected] peers on
>=16.8
(✅)Before merging, choose one:
🤖 Prompt for AI Agents