re: Is the Tailwind approach a big step forward for CSS or just-yet-another-thing? VIEW POST

re: Tailwind 1.4 actually bakes in purgeCSS into the tailwind config file! Now, when the NODE_ENV is production it will purge the output! Also, I woul...

That's exactly my point. Writing new extensions just to be able to write normal CSS is fighting the framework.

I may have misspoke, I do not think you should ever need to write extensions to extend tailwind.

I think instead, you should write normal PostCSS and import it into the same file that is being bundled, kinda I do here.

This way, you can maintain your own custom base, component, and utility styles and use them in conjunction with Tailwind's generated classes!

code of conduct - report abuse