We released v0.17 a week ago and 0.17.1 with many fixes over the weekend.
With the ongoing NPM issues, Our website isn’t updated but there are some notable features, improvements and fixes.
new pstack principle: https://t.co/LIwgXDSO82
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
Stylex is another one of those tools like Relay where it’s annoying to set up, but very worth it because it scales ~infinitely with your codebase. Very happy to see it getting more adoption 😄
@70ki8suda@grok StyleX works with Solid, but the unplugin package may not work with Vinxi. Once Solid Start moves of vinxi to Vite environments, things should work. (This work is in progress)
We recently brought back stylex.attrs which will be nicer with Solid as an alternative to stylex.props
We have a Chrome devtools extension as a beta release.
While it’s great for debugging StyleX it’s also great for atomic styles in general like with Tailwind or PandaCSS
https://t.co/c6s77voULa
@astahmer_dev But also,
- we don’t have features for layers, instead we always show the active styles.
- we group by property not by media query
- editing styles changes the classnames applied
- applying new styles uses inline styles
- easy buttons to remove overrides
.@Meta's @stylexjs is a CSS-in-JS solution for large apps. We look at how it compares to Tailwind on code maintainability, scale and atomic CSS. https://t.co/SVwbpqER6B
.@Meta's @stylexjs is a CSS-in-JS solution for large apps. We look at how it compares to Tailwind on code maintainability, scale and atomic CSS. https://t.co/A5BlpyTgAE
@MidSeasonGroup What would a StyleX MCP do?
So far, we have:
1. A link of LLM resources at https://t.co/boVf6GWkj6
2. A text version of all our docs at https://t.co/9DgCW9YqAr
We will be adding more endpoints for LLMs in the near future.
What else would you like to see?
.@Meta's @stylexjs is a CSS-in-JS solution for large apps. We look at how it compares to Tailwind on code maintainability, scale and atomic CSS. https://t.co/mhUyJqjLgw
- we wanted to dogfood our unplugin package
- we wanted to ensure it also worked with RSCs
- we wanted to do cool CSS things
Waku + Fumadocs seemed to let us do all 3. Although we barely use fumadocs features beyond the mdx processing at this point.
Let’s take a look at Meta’s StyleX — their in-house CSS solution built for scalability. We’ll break down what it is, how it works, and why many believe it could outperform Tailwind for larger projects.
@devongovett StyleX and React Aria work so well together, they really align. My design system uses both. Looking at how Spectrum 2 does styles, it’s very different but has a lot of thematic similarities.
@DamiDina@wongmjane StyleX isn’t a design framework, but a css-in-js compiler. It doesn’t come with any components or default styles.
It’s even less opinionated and flexible than tailwind.
Opinions to be installed separately.