Mateusz Burzyński

Hm, just to make sure that I read this correctly - when installing, let's say, `@emotion/react` we pull in `@emotion/babel-plugin` because it's a regular dependency and it has non-optional peer...

I'm not super keen about it but we also maintain compatibility with SC (unless we feel strongly that it's not worth it) so it might be worth adding support for...

> When the styled tag is picked up by Emotion's babel autoLabel, the [local] name generated will be the name of the wrapper function (StyledEmotionInterop in the above case), and...

https://github.com/emotion-js/emotion/blob/fa977675e1df05f210005ccd3461d6cdaf941b42/packages/babel-plugin/__tests__/import-mapping/import-mapping.js#L9-L38

Well - I would recommend creating a package for your own styled wrapper so you could configure a single entry for the `importMap`. Relative paths makes things worse - although...

The API parity with Styled Components is not a goal. The mentioned concerns expressed here are still very much true. It also doesn't seem like there are a lot of...

Note that we conditionally forward props to the underlying DOM elements (this can be customized with `shouldForwardProp`). If your `hasImage` gets forwarded then it's probably because you are wrapping a...

I'll try to evaluate once again if this is something that we'd like to implement. Note that you can also just wrap `@emotion/styled` in a custom package and just import...

Thanks for filing a report - I've narrowed down the issue to the [`toInputTree`](https://github.com/emotion-js/emotion/blob/ae0f650b5ad8ef658b61edca6157fe208be23b43/packages/babel-plugin/src/utils/minify.js#L21-L39) function and I **think** that I've also recognized how the logic is broken. Gonna be working...

Sorry, this somehow slipped my mind back in May and I've forgotten about this issue. I've prepared a fix for this: https://github.com/emotion-js/emotion/pull/2858