Evan Jacobs

I wonder if synthesizing css variables dynamically to avoid re-injecting styles would have some perf wins… like making it more automatic than this method so you don’t have to manually...

Need to rebase this now that the dependency versions in trunk are pinned to exact versions.

This is something better solved with a middleware IMO. I actually made one for this express purpose: https://www.npmjs.com/package/middleware-proxy

Added a comment to the original issue with a proposed refactoring https://github.com/styled-components/styled-components/issues/3916#issuecomment-2087459577

This change unfortunately regresses hot path performance by a decent amount 

Fix should be here I think, though I don't understand why TS should require an internal type to be exposed https://github.com/styled-components/styled-components/releases/tag/v6.1.10

Are you certain that there is only one copy of styled-components being loaded?

There is another thing to consider: performance. Part of why we target ES5 is the ES5 APIs are actually faster than their ES6 counterparts. ![Screenshot 2024-04-30 at 6 38 23 ...

I ended up taking the other PR, can you check to see if your issue is resolved with current `main` branch?

Thank you for working on this, I have no practical project for streaming testing at this point but I'd be happy to post a test release under a tag for...