Skip to content

fix(deps): replace dependency @material-ui/core with @mui/material#409

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/material-ui-core-replacement
Open

fix(deps): replace dependency @material-ui/core with @mui/material#409
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/material-ui-core-replacement

Conversation

@renovate

@renovate renovate Bot commented Dec 8, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
@material-ui/core (source) → @mui/material dependencies replacement 4.9.145.0.0

This is a special PR that replaces @material-ui/core with the community suggested minimal stable replacement version.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Dec 8, 2024

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @multei/web@0.1.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.0.1" from the root project
npm ERR!   peer react@">=16.8.0" from @emotion/react@11.14.0
npm ERR!   node_modules/@emotion/react
npm ERR!     peerOptional @emotion/react@"^11.4.1" from @mui/material@5.0.0
npm ERR!     node_modules/@mui/material
npm ERR!       @mui/material@"5.0.0" from the root project
npm ERR!     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm ERR!     node_modules/@emotion/styled
npm ERR!       peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.0.0
npm ERR!       node_modules/@mui/material
npm ERR!         @mui/material@"5.0.0" from the root project
npm ERR!   1 more (@emotion/styled)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.2" from @mui/material@5.0.0
npm ERR! node_modules/@mui/material
npm ERR!   @mui/material@"5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-12T17_59_38_010Z-debug-0.log

@netlify

netlify Bot commented Dec 8, 2024

Copy link
Copy Markdown

Deploy preview failed at Netlify. @jimmyandrade take a look please

Name Link
🔨 Latest commit ee57b4d
🔍 Latest deploy log https://app.netlify.com/sites/multei/deploys/6755e2d924d51b0008c0a6f8

@renovate

renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the project’s UI component library dependency by replacing @material-ui/core (Material-UI v4) with @mui/material (MUI v5) in order to move to the community-recommended successor package.

Changes:

  • Replace the @material-ui/core dependency with @mui/material@5.0.0 in package.json.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json
Comment on lines +55 to 58
"@mui/material": "5.0.0",
"@material-ui/icons": "4.9.1",
"@material-ui/lab": "4.0.0-alpha.53",
"@material-ui/styles": "4.9.14",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. This PR cannot be merged as a package-only replacement: the codebase still imports @material-ui/core, and the v4 companion packages (@material-ui/icons, @material-ui/lab, @material-ui/styles, gatsby-plugin-material-ui) would also need a coordinated MUI v5 migration.

I am leaving this blocked instead of merging the dependency swap as-is.

@jimmyandrade jimmyandrade self-assigned this Jul 16, 2026
@jimmyandrade

Copy link
Copy Markdown
Member

Blocked in oldest-PR triage: this is not a safe dependency-only PR. Replacing @material-ui/core with @mui/material requires a coordinated MUI v4 -> v5 migration across imports, theme setup, icons/lab/styles packages, and Gatsby integration. Not merging as-is.

@jimmyandrade

Copy link
Copy Markdown
Member

Created follow-up migration issue: #436. Keeping this PR blocked; not migrating MUI v5 in the oldest-PR drain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants