Mateusz Burzyński

> This is the PR that introduced this feature, but there's no context on that particular line. I don't understand why isRnStyle = type === 'number' In the past RN...

Oh, I have no experience with M1 problems (yet). So can't be of much help here - I would assume this is not a unique problem though so probably there...

A more type-safe way (but not completely) to achieve this would be to namespace your themes in the theme object and implement custom hooks for each one that would select...

Yes, mixing different libraries using the same theming object is a problem and a shortcoming of the styled API. I think it's possible to wrap our `styled` though in a...

We are aware of the "issue". The way how node has implemented support for modules creates a ripple effect on the whole ecosystem - what worked for years in other...

Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the...

The Box component in MUI is not a styled component: https://github.com/mui-org/material-ui/blob/e4b856fdd1686b09357d36c7cefdf0daddfb8bfc/packages/mui-system/src/createBox.js#L12-L25 So we can't "fold" the tree here. cc @mnajdova unsure how feasible that would be but allow this to...

Note for me: we actually only hash the content of the styles and source maps should not affect this anyhow. The problem here is that the second styles have the...

Could you point me to the `components` API docs or something? Would it be impossible to support this API if the component itself would be `styled`?

The problem is that our `/macro` entries depend on `@babel/core`. To satisfy strict package managers we need to declare those. They are declared as optional though so if you are...