The State Of CSS Pre-and-Post Processing
Many of you would probably know that I’m an avid Tailwind user by now — except, I don’t use Tailwind in the traditional way.
When Tailwind 4 hit the scene a couple of months back, I thought it wasn’t possible to use Sass anymore, because Tailwind’s “installation guide” mentions this:
If you tried this in Sass, you’ll run into an error. So I kinda rage-wrote a draft about Post CSS winning the CSS-processing game. 😅
But as I dug deeper and found out more, I realized that —
- While many people have ditched Sass for Native CSS / Tailwind, there’s still a solid use case for Sass.
- You can still use Sass with Tailwind!
- Tailwind WITHOUT Sass is just as great (just, no loops)
So I augmented that draft and created a new article. I call it The State Of CSS Pre-and-Post Processing by my editor at CSS Tricks prefers to rename it to So, You Want to Give Up CSS Pre- and Post-Processors….
Either way, it’s a fine read if you’ve been thinking about your CSS setup.
If your peers have tried to coax you to stop using Sass, Start using Tailwind, or JUST USE NATIVE CSS BECAUSE IT’S GOOD ENOUGH (they say), this post is going to give you a reality check to make a great decision with a calm head on your shoulders.
I hope you have fun reading this one.
Stay awesome,
Zell