Post

CSS-in-JS solves a problem that doesn't exist. It should be clear to everyone from the start that CSS modules are the only correct solution. Combined with BEM, this is the best and most powerful way to style a page. Try to name even one corner case where CSS-in-JS is better. #css

Faster rendering matters most when it leaves the component model easier to reason about. The practical test is whether performance gains reduce complexity instead of moving it elsewhere.

A 55% reduction in SSR time is substantial. I'm curious how much of that reaches users as lower TTFB/LCP versus being absorbed by caches, and whether removing runtime style work improves INP too. Field CWV alongside server timings would help connect the two.

Has this fixed CSS-in-JS though? Is it using native `with {type:css}` imports? Without that, surely it's just an extra compile tool so that developers can work with CSS, but the output is still JS?

I just published a post I have been working on for a while bsky.app/profile/did:...

Attaching styles to html elements. We don’t really have a good way to do that today. CSS modules are ok, but you still have to create two files just to make a button. Vue and Svelte are much better, but there isn’t an equivalent for React to my knowledge.

Looks like you forgot to enable CSS modules production mode for production. I see class names such as "prc-PageLayout-PageLayoutRoot--KH-d SidebarPageLayout-module__PageLayoutRoot__G0dxi" Normally this would be something like "G0dxi" in production.