When building for production, you should always use Tailwind's purge option to tree-shake unused styles and optimize your final build size. When removing unused styles with Tailwind, it's very hard to end up with more than 10kb of compressed CSS.
A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
I think we misunderstood what was needed, and then tried to work out how we'd apply it to our application structure. Ultimately we found a different one which would see us through the short-medium term which let us put in only the components we needed.
I'll have to give Tailwind a proper look over on a project at some point. It has the huge bonus of not being Bootstrap.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
tailwindcss.com/docs/optimizing-fo...
That's really handy.
I think we misunderstood what was needed, and then tried to work out how we'd apply it to our application structure. Ultimately we found a different one which would see us through the short-medium term which let us put in only the components we needed.
I'll have to give Tailwind a proper look over on a project at some point. It has the huge bonus of not being Bootstrap.