[discussion] Preparing v6

[oliviertassinari]

Edited by @DiegoAndai: Moved accepted ideas/issues into either the v6 milestone, the v7 milestone, or this list of brainstorm ideas

This is an umbrella issue that centralizes and lists all the potential improvements that we can consider in MUI Core v6. The potential improvements being listed here require breaking changes. We do not intend to ship v6 in 2022. We plan, as much as possible, to release the next major features in minor versions without breaking changes.

Big features

• Static CSS extraction [system] Support new style engine that generates static CSS files at build time #34826 / [RFC] Zero-runtime CSS-in-JS implementation #38137 A new style engine, an alternative to emotion and styled components, with no runtime (extract the CSS at build time). Many of the fastest growing frontend libraries in 2022 were focusing on performance. Considering the feedback in our survey and the trend in the space where better performance = better UX, we have a great opportunity by pushing in this direction. Now that we can use CSS variables, and that we have the styled API, we should be able to pull this off without a major breaking change. Another reason why https://www.robinwieruch.de/web-development-trends/#utility-first-css.
• React Server components Add React Server Component support for Layout components (Grid, Stack, Container) #35993. For the same reason as above, this can improve performance. Deno, who is heavily biased in the claim raise a few reason why the need for server side rendering trend will continue to grow https://deno.com/blog/the-future-and-past-is-server-side-rendering.

Other changes

For a detailed list of changes, please visit the Material UI: v6 milestone. If you're looking for a particular change, you can also search issues filtering by that milestone.

Promotions

• https://github.com/github/release-radar

[MitchTalmadge]

What change does this fall under?

material-ui/packages/mui-material/src/Tooltip/Tooltip.js

Line 232 in 97427f0

// TODO v6: Remove PopperComponent, PopperProps, TransitionComponent and TransitionProps.

I'm curious for the reason behind removing PopperProps

Edit: It looks like it was added in f98d52b so I believe the reason must be that componentsProps will consume both PopperProps and TransitionProps.