Marija Najdova

It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or...

The `LoadingButton` will be moved to @mui/material in the next major version, we want new components to live in the lab so that we can experiment and collect feedback before...

I don't think we should default to adding more features into components if we can split them - these decision will increase the perception that the components are bloated. I...

> What's the point of maintaining two separate components? Bundle size is the main reason. We are loading another component, the `CircularProgress`, is it worth always loading this as part...

> Q: Could we look into dynamically importing CircularProgress? I assume doing that at the library level can be tricky because bundlers may treat these differently. @romgrk just added lazy...

> Btw, I don't have strong opinion, I am just sharing the historical reason for it. We should be cautious when making API decisions in general into what is most...

Yes you can, you can use the `@pigment-css/unplugin` package. Here is an example `webpack.config.js` file: ``` const { webpack: PigmentPlugin } = require('@pigment-css/unplugin'); const { createTheme } = '@mui/material'; //...

Everything is prepared from infra side, we need to enable it per repository and fix all the issues that will appear.

For the duplicated issue, can we rephrase to: > Thank you for reporting this issue. However, it seems to be about the same problem as described in issue #[issue number]....

It's hard to know what may be miss-configured without a repo example to look into. Can you create a simpler reproduction and share link to the repository? Thanks!