Skip to content
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

[material-next] Drop the package #41544

Merged
merged 6 commits into from
Mar 18, 2024

Conversation

mnajdova
Copy link
Member

@mnajdova mnajdova commented Mar 18, 2024

We are dropping the @mui/material-next package. We are already working on the next Material UI version, which is about allowing static CSS extraction. We don't have the bandwidth to keep the focus on both of these efforts at the same time, and it is a maintenance burden to keep the package alive.

Once we start to work on v7 and focus on the design-related updates, we will be directly updating the Material UI components, likely working on the next branch alongside the ongoing stable release.

@mnajdova
Copy link
Member Author

I wasn't sure if I should update the second part of https://mui.com/blog/2023-material-ui-v6-and-beyond/#material-ui-v7, where we mention the package. I left it for now.

Copy link
Member

@DiegoAndai DiegoAndai left a comment

Choose a reason for hiding this comment

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

  • Will he latest released version of the package still be available to users?
  • Should we keep the components' "Material Design 3 version" section? I think it's better to add a callout explaining that the material-next package is not being worked on while we wait to start working on v7. Simply removing it seems that it might scare people.

@mnajdova
Copy link
Member Author

Will he latest released version of the package still be available to users?

Yes, I don't plan to remove it from npm now. We are discontinuing the work on it.

Should we keep the components' "Material Design 3 version" section? I think it's better to add a callout explaining that the material-next package is not being worked on while we wait to start working on v7. Simply removing it seems that it might scare people.

I think it may be misleading to keep the demos, we do not want people to keep experimenting with this package, that was the sole purpose for adding these. Based on the number of downloads I wouldn't worry: https://npm-stat.com/charts.html?package=%40mui%2Fmaterial-next&from=2023-03-17&to=2024-03-17

@DiegoAndai
Copy link
Member

I think it may be misleading to keep the demos

Good point. Let's go ahead then.

We can leave a comment in #29345 explaining why those were removed.

I wasn't sure if I should update the second part of https://mui.com/blog/2023-material-ui-v6-and-beyond/#material-ui-v7, where we mention the package. I left it for now.

I would update it, under the same argument that we're removing the demos.

@mnajdova
Copy link
Member Author

I wasn't sure if I should update the second part of https://mui.com/blog/2023-material-ui-v6-and-beyond/#material-ui-v7, where we mention the package. I left it for now.

I would update it, under the same argument that we're removing the demos.

Fair enough, updated and I also updated the all components page to not show the MD3 tags anywhere.

@mnajdova mnajdova merged commit 6da671c into mui:master Mar 18, 2024
22 checks passed
@DiegoAndai
Copy link
Member

Fair enough, updated and I also updated the all components page to not show the MD3 tags anywhere.

cc: @danilo-leal

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.

3 participants