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 would argue that the things you talk about needing to "fight the framework" is just stuff you should be extending to tailwind with something like postcss imports!
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!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.