-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade Material UI v4 to v5 (@material-ui
to @mui
)
#469
Labels
Comments
nelsonni
added
bug
Bug reports or bug fixes
feature
Feature requests or improvements
dependencies
Issues or updates to dependency files
labels
Jul 8, 2021
v5.0.0-beta.3 was released 2 days ago. |
The article, Material-UI makeStyles, useStyles, createStyles, and withStyles Explained by Jonathan Middaugh, provides a good explanation of the Material-UI's |
nelsonni
changed the title
Upgrading to Material-UI@5
Upgrading from Material-UI v4 to MUI v5
May 19, 2022
nelsonni
changed the title
Upgrading from Material-UI v4 to MUI v5
Upgrade Apr 19, 2023
@material-ui
v4 to @mui
v5
nelsonni
changed the title
Upgrade
Upgrade Material UI v4 to v5 (Apr 27, 2023
@material-ui
v4 to @mui
v5@material-ui
to @mui
)
Resolved in Synectic v4.0.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Material-UI v5 has been released. Several breaking changes are included, with the first beta release v5.0.0-beta.0 including several in their release notes. This release will also begin to provide more hooks-based solutions to props functions.
@material-ui/styles
to@material-ui/styled-engine
; based on v5 deprecation ofmakeStyles
/withStyles
[styles] Dynamic makeStyles unexpected behavior mui/material-ui#15511 (comment) and [docs] Replace makeStyles/withStyles with sx prop and styled mui/material-ui#16947.Additional considerations must be resolved prior to upgrading Synectic to Material-UI@5. The best resource is going to be the Migration from v4 to v5 Guide.
The text was updated successfully, but these errors were encountered: