Michał Dudak

Yes, that is correct. We are going to redesing the Autocomplete from the ground up, so there is no point in optimizing it today. As for other improvement areas, I'll...

@hbroer you are touching a different subject: https://mui.com/material-ui/guides/minimizing-bundle-size I'm returning to this issue as the @mui/core team leans toward named exports. Additionally, based on the number of votes on the...

I wonder if #31835 is also related to default exports.

I'm not in a position to decide whether to include it in Material UI, but we will discuss including it in Base UI.

Great initiative! I'd change how the description is displayed, however. Could it be similar to parameter descriptions? I'd also change the word "templates", as it's not really a TS lingo...

@LukasTy, do you still intend to work on this?

At MUI, we're also having a hard time upgrading to 11.11.0. It manifests itself in a pretty weird way, claiming that one of our functions is not a function: https://app.netlify.com/sites/material-ui/deploys/646362611ccf2300088a7a54#L111...

Thanks for the detailed investigation, @emmatown! I opened an issue in next.js: https://github.com/vercel/next.js/issues/49898

We're aware the documentation is lacking in this regard. We're going to update it before the stable release.

This will be closed once the changes introduced in https://github.com/mui/base-ui/pull/818 are propagated to all the pages.