Turns out the website deploy went through after all!!

stylexjs.com/blog/v0.17.1/

The new unplugin is phenomenal

If you bounced from stylex cause the 3rd party Vite integrations were bad, now is the time to try again

Developers that go all in on StyleX tend to stick with it!

Try the new version of StyleX with the new features and the new unplugin package with your Vite apps. (Including with RSCs)

And tell us what you think!!

Additionally, we’ve tweaked some of the default configuration options which affects what you’ll see in your dev tools during development, and improved file paths for finding the source of your styles.

We’ve also fixed a bunch of bugs including a subtle bug with generating media query strings.

StyleX The styling system that powers Meta.

Our new APIs DO NOT break our consistency and composition guarantees.

We allow “observing at a distance” not “styling at a distance.

stylexjs.com/docs/api/jav...

These APIs let you observe some other element that is “marked” with either
- stylex.defaultMarker()
- or a custom marker created with stylex.defineMarker()

Again, this is similar to group or named groups in Tailwind.

stylex.when.* APIs

We have shipped new APIs that finally gives you the ability to style conditionally based on the state of some *other* element.

This is similar to Tailwind’s “group” and “peer” classes, but in all directions:
- ancestor
- descendent
- siblingBefore
- siblingAfter
- anySibling

Note: Next.js is not yet supported with the unplugin package as it uses a complex multi-process webpack setup and Turbopack hasn’t shipped a plugin API yet.

We look forward to having a first class integration with Next once Turbopack ships their plugin API.

The new unplugin package supports a variety of well known bundlers and we have expanded the examples in our repo to specifically test various Vite-based setups.

This new plugin should be easier to setup, faster and more reliable than the PostCSS plugin.

Please tell us if you still face challenges.

All new unplugin package.

Ever since we first open sourced StyleX, integrating it with various bundler setups has been one of the biggest challenges.

So far, the PostCSS plugin has been the smoothest experience we’ve been able to offer so far, but we knew we could do better.

StyleX The styling system that powers Meta.

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.

stylexjs.com/docs/api/jav...

StyleX The styling system that powers Meta.

stylexjs.com/docs/api/jav...

With support for descendent/sibling/descendent selectors coming soon, what are your biggest remaining wants from StyleX?

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.

StyleX The styling system that powers Meta.

In a well deserved FINALLY, a functional playground for StyleX is now live!

Try it out now:
stylexjs.com/playground

As a bonus, the link takes you to a basic Vite example app

Release 0.10.0 | StyleX Happy new year! We are excited to announce the release of StyleX v0.10.0, which includes several new features and improvements.

… 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/

Variants | StyleX The "variants" pattern allows you to conditionally apply one of several predefined styles based on a value.

🍱 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.

Release 0.10.0 | StyleX Happy new year! We are excited to announce the release of StyleX v0.10.0, which includes several new features and improvements.

Happy new year!

StyleX v0.10.0 is now out. This is a consequential release as it comes with out PostCSS plugin, making integrating StyleX into your Next or Vite app dramatically easier.

Read all about it or follow along for the highlights.

stylexjs.com/blog/v0.10.0/

🥳 1 year old!

@stylexjs.bsky.social was open sourced exactly one year ago, and today, one year later, here is the other project that is at least a couple of years overdue: React 19

Vite + React + StyleX - StackBlitz Next generation frontend tooling. It's fast!

Here’s the newest, and simplest way to setup StyleX in a Vite project:

stackblitz.com/edit/vitejs-...

Just merged a PR that adds postcss-plugin for StyleX.

Using StyleX with Next just got a whole lot easier!

The best way to write Tailwind will be….

… @stylexjs.bsky.social

Release 0.9.3 | StyleX StyleX v0.9.3 is now available with some big improvements and bug-fixes.

Read the full release notes here:

stylexjs.com/blog/v0.9.3/