[material-ui] Questions regarding Pigment CSS usage

Related page

https://mui.com/blog/introducing-pigment-css

Kind of issue

Missing information

Issue description

Sorry if this is not the best place to discuss this, I was not sure where to, if you have a better place please point me to that! :)

My team has a very specific way of using material-ui, we expose our components for usage in TypeScript and Dart. Pigment seems to depend on source transformations which would be fine for our TypeScript consumers but would possibly be a hard stopper for our Dart consumers, unless we are able to provide similar functionality with a custom dart build step.

So questions:

1. Will Pigment be the only way to use mui-material going forward? or will it be an optional dependency? Meaning could we continue to use emotion as our sx & styled engine even after Pigment?
2. Are there plans to drop support for Emotion at some point? If not, will there be disadvantages to staying on Emotion?
3. Will sx continue to work on material-ui components under Emotion, even without Pigment's source transformations?
4. Is there possibly alternate ways to use Pigment that doesn't require source transformations?

Context

No response

Search keywords: pigment, css-in-js, emotion, css