Post

You might have missed this, but on X everyone is talking about StyleX lately 👀 Here's our latest headline to catch up

Seb ⚛️ ThisWeekInReact.com@sebastienlorber.com

This Week In React 295 ⚛️ - StyleX - browser() - Next.js - Compiler in Vite/Bun - Astryx - Formisch - React Aria - TanStack 📱 - C++ API - Margelo+Callstack - Observe - Reanimated - Teleport - Nitro - Screen Transition 🍿 Read thisweekinreact.com/newsletter/295 ✍️ @jwr.ski & I

fry69

@fry69.dev

There seems to be a pipeline from this post by Jared Palmer (Devin/Cognition) ->

3/9/26, 8:29 am0 reposts0 likes

fry69

@fry69.dev

3 Sept

Which led to the discussion on SyntaxFM -> www.youtube.com/watch?v=NIG9... I think this reevaluation since the advent of LLMs about marrying CSS and JavaScript is warranted. Outside an enterprise setting dominated by generated code this approach may be a bit more questionable though.

youtube.comWhy is everyone moving to Stylex?YouTube video by Syntax

fry69

@fry69.dev

3 Sept

For small sites/snippets/web components/etc LLMs are perfectly capable to understand and grasp CSS, even if it resides in a different file, is a bit separated from Javascript. Related ->

Dave Rupert@davatron5000.bsky.social

Watched the @syntax.fm episode on how everyone's moving from Tailwind to StyleX and while I'm sure it's great, but it dawned on me that I haven't had "How do I write styles without scoping issues!?!?" problems in a long time. In #webcomponents, you write CSS. www.youtube.com/watch?v=NIG9...

youtube.comWhy is everyone moving to Stylex?YouTube video by Syntax