Keeping a running list now: - pretty much any web surface at Meta - FB/IG Quest apps via RSD - Figma - Snowflake - Hubspot - Linear - Polar - Mixcloud - co/core (new launch)

And there’s still scope to do a lot better. The components can be better. The usage of StyleX can be better. I’m working on something, but it’s not ready yet.

check out Meta's new OSS component library, built with @stylexjs <3

A deep dive from our engineer @kenneth_skovhus on why we're moving Linear from styled-components to StyleX, and what we've learned so far.

Great article and you get a great reward for reading in the form of a styled-components to stylex codemod.

Disclosure: I am a former maintainer of StyleX at Meta.

As a first blog post, I'm writing about how @polar_sh is steering away from Tailwind to StyleX in an effort to futureproof our frontend. Making it impossible to express an off-brand decision. If a value isn't a design decision, it should not typecheck. What do you want to know?

didn't know linear was already migrating to stylex too

We’ve just completed yesterday a 3,000 component refactor from styled components to stylex, no regrets. Solid speed up, types and better predictability. Also the css output is tiny!

We migrated Mixcloud over as well, just sunset all other style systems.

Other than Meta, some notable companies using StyleX are: Figma Polar Linear Hubspot Snowflake

More validation! The team is seeing exactly the same wins that we did while first building and using StyleX for the facebook web rewrite.

thank you for inspiring this syntax !! still experimental, we'll share some release notes docs soon!

I'm excited to share that I’ll be joining OpenAI next month as a Member of Technical Staff. 🎉 I'll be joining the ChatGPT Web Infrastructure team in London.

new pstack principle: github.com/cursor/plugins/bl… this was actually a cool emergent behavior i noticed while tackling a really large refactor to @stylexjs. my agent using /poteto-mode started writing codemods and custom skills for its subagents as it tried parallelizing moving components over. turned it into a principle, so now whenever you invoke /poteto-mode on a large enough task, your agent will build tools for itself.

ICYMI, you *can* use StyleX DevTools with Tailwind, too. The biggest benefit right now is being able to cleanly override styles. - Suggests values from your CSS and changes the actual classNames on elements. - Applies inline styles when a new CSS value is used - Easy reverts