Mateusz Burzyński

> If a maintainer could grant my builds to run, that'd be very helpful. 😄 I hate that GitHub "feature" >.< Can I somehow grant you permission to run builds?...

@sarayourfriend `@emotion/sheet`, `@emotion/unitless`, `@emotion/memoize`, `@emotion/weak-memoize` and `@emotion/is-prop-valid` are the easiest picks right now

Yes, definitely! Thanks a lot for your contributions. I've seen all of them but I'm being slammed lately with work and didn't find the time to sit down to this...

@Beraliv thank you for the offer! It feels like we should now take care of `@emotion/cache` and `@emotion/serialize`, after that we can try to convert `@emotion/css` and `@emotion/server`, which would...

Probably not that much has changed on the main branch since the last merge - i will merge it to the ts-migration soon. Feel free to migrate anything and just...

> In the packages that have already been migrated, we still have .d.ts files, tslint.json, and type checking tests. Is it safe to remove all of this stuff? This is...

I'm actually not sure - perhaps we should do some digging in the issues, the original PR etc to see if there was any specific reason to not use this...

@igorovic perhaps you could figure out how to fix this based on [this](https://github.com/emotion-js/emotion/issues/2803#issuecomment-1173669214). IIRC the issue was awfully similar there and I've managed to make it work.

The problem, most likely, is that your components have no common Emotion-aware ancestor. Try wrapping the whole thing in the `CacheProvider` - it should help you.

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