The PostCSS plugin does very little here. It’s just an integration point or a glorified string replacement engine.

We will continue to lean on LightningCSS for any future style transformation needs.

… and other small bug fixes and improvements.

There are other, less splashy but important improvements.

Read all about the release in our release notes:

stylexjs.com/blog/v0.10.0/

🍱 Recipes section in documentation

We added a new “recipes” section to our documentation to provide example patterns for using StyleX.

Please keep your questions coming and we will add to this section as time goes on.

stylexjs.com/docs/learn/r...

🖥️ CLI improvements

The CLI is faster by leveraging a filesystem cache, supports usage of other syntax transforms and works correctly on Windows.

Further improvements are coming soon and the PostCSS plugin will start getting these benefits too.

📂 rootDir no longer needed for theming

StyleX now resolves the nearest package.json file automatically and doesn’t need a manually configured rootDir for the theming APIs

(Soon: automatic alias configuration!)

🧹 ESlint improvements

Among other improvements, the StyleX ESlint plugin now includes a “no-unused” rule for detecting unused styles.

🛠️ Better Debugging

StyleX has a new `debug` option to make classnames and variables more readable in development.

Compiler error messages are also hugely improved and should pinpoint the exact problem in a lot more scenarios.

⚡️PostCSS plugin!

This release launches a PostCSS plugin that makes integrating StyleX into a Next or Vite app dramatically easier and much more reliable.

Read the full release notes here:

stylexjs.com/blog/v0.9.3/

Pseudo Elements and Pseudo Classes all mixed up, now work correctly.

And our ESLint plugins and Typedefs know about more of them.

Dynamic Styles are better than ever

Dynamic styles now handle "null" values more efficiently and correctly.

"rootDir" is now optional and ESM imports work more reliably.

Theming APIs

StyleX themes are now exclusive and you won't accidentally end up with values from two different themes for the same VarGroup.

Also, reset themes are now as easy as:
stylex.createTheme(varGroup, {})