Mateusz Burzyński
Mateusz Burzyński
This is still very much an issue
This is still very much an issue
What are you blocked on? Emotion 11 should still work with React 19, it just doesn't benefit from some new APIs that we could use with React 19
Then this PR doesn't (yet) contain the changes you need. You need this PR: https://github.com/emotion-js/emotion/pull/3295 . The problem with it is that style rendering in browsers (on the client side)...
If your site is mostly static then that perf degradation wouldn't really affect you but it's hard to justify merging that PR and releasing a prerelease version when we know...
A runnable repro case has to be provided to investigate this - although I strongly suspect the issue is not really on the Emotion side of things.
Since `interpret` is exported from the root entry we could do this with the help of `typesVersions`. We could use an improved version of this: ```ts export declare function interpret<...
> This makes it impossible to set any initial state based on external data. Here's a simplified example for context: This would be a canonical use case for `input`
1. This would inherently allow for hydration mismatches to happen. Im not sure what Vue does in such cases but it’s definitely something that should be discouraged and avoided. The...
> ArkType version: 2.0.0-dev.13 There is no such version 😉