What Astro learned from the secret Applebee's training facility, a new use case for WebContainers, and a type-friendly way to spend your Friday night.

Bytes by ui.dev

New CSS-in-JS libraries are emerging, potentially due to React server components and other new React features. These features allow for better server rendering and the ability to load styles on demand. The article explores the reasons behind the resurgence and how React 19 handles script and style tags.

CSS-in-JS is so back

With css gaining more and more features I think the pros in using CSS-in-JS alternatives are becoming less overtime. I love js, I even worked a lot with the styled api (material UI, styled-components, emotion) and the DX was awesome, but in certain cases it can become a nightmare.
I found that vanilla CSS with css modules are more resilient and easy to adopt and maintain, after all it’s just css scoped to a certain module (and works great with code splitting and SSR).
Also there are new css engines coming like <a href="https://unocss.dev/guide/why" target="_blank" rel="noopener nofollow">unoCSS</a> that are worth check.

Quite astounding, how we run away from writing normal, “classic” CSS and running towards having everything in JS.
I was a huge fan of Styled Components, and made a ton of projects (commercial and not) with it, but now I see how complex and full of overhead it is, when compared to writing CSS the old way.

How did we end up here? Pure CSS in a .css file used to be perfectly sufficient. Yet, over the years, we’ve reinvented the wheel, making everything more complex. Nowadays, setting up the boilerplate for even a simple one-page site takes too much time. Ugh… 😅

ever heard of htss
html in css in js