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)
We have a new RFC for bringing custom enums to StyleX.
It’s syntax sugar around CSS variable toggles aka space hack to let you define a variable somewhere and then use that as a condition within CSS values.
Our API works with enums and stylex.match
Stripe's design system components accept a css prop, bound to design system tokens and supporting custom plugins. Under the hood it's (now) powered by stylex.
It’s obvious that our documentation of the value of “type-safety” isn’t clear enough. Would love some ideas on how we can make it better.
Also feedback about documentation in general is very welcome!
@syntaxfm put out a great video about StyleX today, but it also revealed that many don’t understand what we mean when we talk about type-safety.
youtube.com/watch?v=NIG9Gb…
