Skip to content

Replace dependency @material-ui/core with @mui/material #5458

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.

Sign up for GitHub

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
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Replace dependency @material-ui/core with @mui/material #5458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
},
"dependencies": {
"@fancyapps/fancybox": "^3.5.7",
"@material-ui/core": "^4.2.1",
"@mui/material": "^5.0.0",

@sentry sentry Bot Feb 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The dependency update to MUI v5 is incomplete. All import paths and API calls in the code still reference the old v4 package and function names, which will break the build.
Severity: CRITICAL

Suggested Fix

Update all import statements from @material-ui/core to the new @mui/material package. Run a codemod or manually refactor the code to use the new v5 APIs, such as renaming createMuiTheme to createTheme and MuiThemeProvider to ThemeProvider.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The pull request updates Material-UI from version 4 to version 5 in
`package.json` but fails to update the corresponding code. The entire codebase still
contains over 100 import statements from the old package name, `@material-ui/core`,
which has been removed. Additionally, the code uses v4 APIs like `createMuiTheme` and
`MuiThemeProvider`, which were renamed to `createTheme` and `ThemeProvider` in v5. These
issues will cause the application build to fail with module resolution errors,
preventing deployment.

Did we get this right? 👍 / 👎 to inform future reviews.

@sentry sentry Bot Mar 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The dependency @material-ui/core was upgraded to @mui/material v5, but the codebase was not migrated, causing fatal import errors and breaking API changes.
Severity: CRITICAL

Suggested Fix

Follow the official Material-UI v4 to v5 migration guide. Run the automated codemods to update package names, imports, and common API changes (e.g., createMuiTheme to createTheme). Manually review and fix any remaining breaking changes, such as component prop updates (e.g., Checkbox onCheck to onChange).

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The `package.json` is updated from `@material-ui/core` v4 to
`@mui/material` v5, but the application code has not been updated to reflect this major
version upgrade. The codebase contains over 140 files that still import from the old
`@material-ui/core` package. Since this old package will no longer be installed, the
application will fail to start due to module import errors. Additionally, even if the
imports were fixed, the code uses APIs like `createMuiTheme`, `MuiThemeProvider`, and
component props like `onCheck` and `inputStyle` that were renamed or removed in v5,
which would cause runtime failures.

@sentry sentry Bot Mar 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The upgrade to @mui/material v5 is incomplete, as it requires React v17+ and the peer dependencies @emotion/react and @emotion/styled, which are missing.
Severity: CRITICAL

Suggested Fix

Update the react and react-dom dependencies to version 17.0.0 or higher. Additionally, add the required peer dependencies for MUI v5 by running npm install @emotion/react @emotion/styled.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The project's `package.json` is being updated to use `@mui/material`
v5, but this upgrade is incomplete, introducing multiple issues. Firstly, MUI v5
requires `react` version 17.0.0 or higher, but the project is configured to use `react`
version ~16.8. Secondly, MUI v5 has required peer dependencies, `@emotion/react` and
`@emotion/styled`, which have not been added to the `package.json`. While there is a
more immediate build-breaking issue due to outdated import paths in the code, these
dependency incompatibilities will cause application failures once the import paths are
corrected.

@sentry sentry Bot Mar 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The application will fail to start because it still imports from @material-ui/core, which is being removed as a dependency in favor of @mui/material.
Severity: CRITICAL

Suggested Fix

Update all import statements throughout the codebase to use the new MUI v5 package names. For example, change imports from @material-ui/core to @mui/material. Also, update API calls that were renamed, such as createMuiTheme to createTheme and MuiThemeProvider to ThemeProvider.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The `package.json` is updated to replace `@material-ui/core` with
`@mui/material`, but the codebase still contains numerous import statements referencing
the old package, such as `import { MuiThemeProvider, createMuiTheme } from
"@material-ui/core/styles"`. Since the `@material-ui/core` package will no longer be
installed, these imports will fail during module resolution. This will cause the
application to crash on startup or fail during the build process, preventing it from
running.

@sentry sentry Bot Mar 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The Checkbox component is passed an onCheck prop, which was removed in MUI v5. This will cause checkboxes to be unresponsive to user clicks.
Severity: HIGH

Suggested Fix

Update all instances of the Checkbox component to use the onChange prop instead of onCheck. Additionally, review the entire codebase for other MUI v4 to v5 breaking changes, such as renaming createMuiTheme to createTheme and updating all import paths from @material-ui/core to @mui/material.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The application's dependency was updated from Material-UI v4 to MUI v5,
but the code was not updated to reflect the breaking API changes. Specifically,
components like `Checkbox` are still being passed the `onCheck` prop, which was replaced
by `onChange` in v5. While the application will fail to load due to incorrect import
paths (e.g., using `@material-ui/core` instead of `@mui/material`), if those paths were
corrected, this underlying API mismatch would cause a functional bug. Checkboxes would
not respond to user clicks because the event handler is attached to an unrecognized
prop, breaking functionality in areas like profile forms.

"@mitodl/iso-3166-2": "^1.0.1",
"@sentry/browser": "^6.4.1",
"@sentry/webpack-plugin": "^1.18.3",
Expand Down
Loading