6 ms·

tailwind is 1.7MB of CSS? ....whyy?

• uryga 6y ago
  id imagine that you get a lot of rules when you have a whole bunch of different "margin-top-<x>". the idea is probably to rely on some CSS tree-shaking/"dead CSS elimination" tool to only keep the ones you need
  • julienbourdeau 6y ago
    exactly
• zambal 6y ago
  It defines css classes for most css properties. Their website [1] explains why you might want that pretty well. Regarding file size, the idea is that you use something like PurgeCSS in your build pipeline, which removes all unused css classes. A bit like tree shaking for css. [1] https://tailwind.css https://tailwind.css
  • jedieaston 6y ago
    https://tailwindcss.com https://tailwindcss.com is the link :D
  • giancarlostoro 6y ago
    Additionally so you can open up the developer tools, and just slap on classes on divs and experiment a bit quicker. Towards the end you can put it all together and trim it down, not sure if there's tooling that auto joins some of the CSS as necessary though.