Mateusz Burzyński

This is because we explicitly allow other properties: https://github.com/emotion-js/emotion/blob/fc119766b539f73546dc8e2863cca1439af3cb1c/packages/serialize/types/index.d.ts#L37-L40 I'm not entirely sure why though, most likely to support non-standard properties that are not covered by `csstype`.

Oh, I thought right now about an even more important reason why this is like it is. It allows writing things like: ```js css({ ':hover,:focus': { color: 'hotpink' } })...

As to your `Style` example: ```js const styles = { color: 'hotpink', 'div': { color: 'green' } } ``` This `styles` object is not assignable to `CSS.Properties`, nor it is...

> The workaround I found was to include the comment in the previous block. Based on some quick debugging, it seems like all the comments are getting put into the...

How much of a real-world impact this can have? You have kinda created a microbenchmark there - where also you were able to speed up some things by caching **without**...

I've added such tests locally and they pass: https://github.com/emotion-js/emotion/commit/6f678f894623ab3a7c18074fd7d6a5f59763d037 You'd have to provide a full runnable repro case for me to investigate it any further.

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...

This really looks like a problem with your bundler - the stack trace points to `stylis.mjs` but you might check that this file doesn't contain a reference to `exports` variable...

Could u create a repro case for this? Im not that well-versed in those advanced possibilities of Rollup and it would be easier for me to understand this if I...

Hm, filtering options have been on purpose not implemented for Babel output plugin by @lukastaegert: https://github.com/rollup/plugins/blob/2623f390c3385fcaf3a3072e8e6c0ec71f6ad114/packages/babel/src/index.js#L177-L182 Maybe he could shed some light if adding support for this is a good...