The styling system for the modern web * 🌐₊˚
- Tweets 344
- Following 48
- Followers 1,951
- Likes 400
You can expect the next release of StyleX very soon. We're hard at work making some massive improvements to Dynamic Styles.
1
1
22
776
In case you missed it, StyleX v0.8.0 was released this weekend.
It contains improvements to our ESLint plugin, theming improvements and an introduction of lightningcss to our Rollup plugin.
1
7
501
Read the entire Changelog here:
stylexjs.com/blog/v0.8.0/
1
1
210
StyleX retweeted
“Style Sheet Script” (SSS, 3S, Triple S etc)
“TypeStyle” (except that’s TS)
“PaCT” (Presentation at Compile Time)
1
1
946
StyleX retweeted
Yo! Let's make the unified naming happen 🤝
Some ideas:
- CAC (Complied Atomic CSS). Similar to CACTSS but shorter
- CTS (Compiled Typesafe Styling)
- A funny one, V0-CSS, to mean Void zero CSS in JS (no runtime css-in-js)
1
1
12
720
StyleX retweeted
🌵
CACTSS - Compiled and Composable, Typed Styling System?
(Pronounced “Cactus”)
3
2
11
1,572
We’ve trying to come up with a new term for “compile time css-in-js” as that is awkward to say every time.
Any ideas?
- Here’s a horrible idea to get us started:
JSStN (aka “Justin”) for JavaScript Styling Notation?
- CSS as JS?
Good point. I don’t remember starting any kill campaigns. I do remember large customers telling us about the runtime cost of some CSS-in-JS solutions hurting their apps though. I think Tamagui has been very thoughtful about perf and perhaps “CSS-in-JS” is not doing it justice
19
1
27
10,933
StyleX retweeted
I also like @stylexjs! My bias is towards 1️⃣ solutions that help CSS scale w/o conflicts aka composition [which you have in spades] and 2️⃣ solutions that make devs productive / happy. Tailwind checks these 2 boxes for me today.
A nice to have would also be 3️⃣ solutions that work seamlessly in React Native. (Do react-strict-dom and nativewind meet this requirement?)
1
17
3,570
StyleX retweeted
i love css-in-js actually
Tailwind is often seen as the “default” these days and a lot of people love it. Despite that Next still ships with css modules by default and the team has been nothing but supportive to us.
@rauchg is allowed to have his own opinions.
Our job is to change them!
3
2
20
5,071
Tailwind is often seen as the “default” these days and a lot of people love it. Despite that Next still ships with css modules by default and the team has been nothing but supportive to us.
@rauchg is allowed to have his own opinions.
Our job is to change them!
The very first approach to CSS we tried was CSS-in-JS (`next/css` shipped glamor by @threepointone).
Tailwind is a great default because it's performant, *composes excellently* and fixes a lot of CSS gotchas (like declaration order side effects), and very popular in the ecosystem.
I didn't push for tailwind contrary to your statements, I actually came around to it. I think it's a great project, and always open minded to alternatives.
1
3
103
24,211