What working with Tailwind CSS every day for 2 years looks like

Re:What working with Tailwind CSS every day for 2 years look... by whacked_new on Tuesday November 29, 2022 @12:24PM (#33790411)

Thanks for the vanilla-extract recommendation, I'll be using this!

In my case, tailwind was useful for providing a handy set of vocabularies for simple and common stylings. But once customizations start to pile on, we're back into SCSS. Using 2 systems at once meant additionally gluing them with the postcss toolchain, so effectively we have 3 preprocessors running for every style refresh.

Looking in at TypeScript from the clojurescript ecosystem though, I'm still yet to see an equal to https://github.com/noprompt/garden or https://github.com/Jarzka/stylefy: single language, excellent composability, compile-time anonymous class names, inline styles... almost like they solved CSS (except for typing)

that said, tailwind's and SCSS's VS code integration is pretty amazing.

[ Parent | on HN ]

Re:What working with Tailwind CSS every day for 2 years look... by stephen on Tuesday November 29, 2022 @12:58PM (#33790867)

Fwiw to the avoid 80%-in-TW / 20%-in-SCSS-or-something-else dichotomy/complexity, we built Truss which brings TW (Tachyons) style abbreviations to the existing "something else" tool chain (Emotion in our case).

So then everything goes through a single system.

https://github.com/homebound-team/truss

> tailwind's and SCSS's VS code integration is pretty amazing

We get that too, by being just vanilla TypeScript, no editor-specific integration necessary. :-D

(I've linked to Truss in another response, so will stop now. :-))

[ Parent | on HN ]