Michał Dudak

One concern that I have is that the "modern" condition may be used by another package as well, and since we can't control conditions per import, configuring a bundler to...

The Tooltip [is being reimplemented in Base UI](https://github.com/mui/base-ui/issues/32). @atomiks, could you take this issue into consideration when working on the new version?

I don't have a strong preference, so let it be `packages-internal`.

MUI X integration: https://github.com/mui/mui-x/pull/12142

I tried playing with the second autocomplete in the [Playground](https://mui.com/material-ui/react-autocomplete/#playground) but I couldn't see any issues (Edge 123 on Windows 11).

I can't figure out why the TextareaAutosize test suddenly started to fail.

> Why not enforce the code to move in sync with a single npm package? I am the supporter of multiple smaller packages here. Having several fine-grained packages scales better...

> This is the value I see on my end with a single npm package: back pressure: As I understand the example of the pain: someone did too many debt...

> And it guarantees better that we don't end up with that one repository where some forgotten package stays forever on an old version I agree that a single large...

I updated the proposed list of packages in the shaping doc on Notion and started working on the internal-scripts package (#41079)