NEVER, ever use Tailwindcss without purgeCSS to clean it up on production. Otherwise you will be shipping 780KB of css (in 2.0 this will be probably over 1MB, and rapidly growing with plugins and customizations), from which you will be using 1% of it.
Those couple lines of code in postcss config is why Tailwind is so great in the performance department.
NEVER, ever use Tailwindcss without purgeCSS to clean it up on production. Otherwise you will be shipping 780KB of css (in 2.0 this will be probably over 1MB, and rapidly growing with plugins and customizations), from which you will be using 1% of it.
Those couple lines of code in postcss config is why Tailwind is so great in the performance department.
Example config: github.com/pavelloz/webpack-tailwi...
Official docs explanation: tailwindcss.com/docs/controlling-f...
Good callout. It can be easy to miss this concern when first getting started with TailwindCSS.
This is a great point. I will be doing a follow up to this for adding purgecss.