fix: update peer dependencies to support newer versions of MUI packages #1493
+3
−3
Conversation
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
|
@vostrypet is attempting to deploy a commit to the Kevin Vandy OSS Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Change: Expand peerDependencies in package.json to support MUI v7 alongside v6 (@mui/material, @mui/icons-material, @mui/x-date-pickers now >=6 || ^7.0.0).
Reason: Allow projects on MUI v7 to use material-react-table without forks or local overrides.
Real-world verification: We are using material-react-table with MUI v7 in our project, where we overridden the peer ranges in package.json to >=6 || ^7.0.0. Everything works smoothly—components, styling, and interactions are fully compatible.
Compatibility: MUI v6 remains supported; this is a semver range extension only.
Impact: No API or build changes; safe peer dependency update.