News for hackers. Stuff that matters.

A comment on Building React and Vue Support for Tailwind UI. Parent comment

Re:Building React and Vue Support for Tailwind UI by cageface on Tuesday April 13, 2021 @10:11AM (#26792365)
I have a few hundred tailwind classes left in my projects after a purge css pass. If you have thousands you probably should start looking into extracting some components. If you literally have "a few thousand" colors in your UI you need to find a new designer.

And CSS variables are great but way more verbose and still require you to come up with "semantic" names for everything.

[ Parent | on HN ]
Re:Building React and Vue Support for Tailwind UI by nailer on Tuesday April 13, 2021 @10:39AM (#26792756)
> If you have thousands you probably should start looking into extracting some components.

This is confusing component reuse with design system reuse.

Two components may have completely different purposes, but they both have a certain rounding, palette, and other styles.

[ Parent | on HN ]
Re:Building React and Vue Support for Tailwind UI by cageface on Tuesday April 13, 2021 @10:54AM (#26793005)
@apply is your friend here.
[ Parent | on HN ]
Re:Building React and Vue Support for Tailwind UI by nailer on Tuesday April 13, 2021 @01:14PM (#26795617)
100% agreed that sharing styles with @apply is exactly how to solve this.

However Tailwind tells users they shouldn't be doing this, encouraging them to paste the same mixins on every element they want them.

[ Parent | on HN ]
Re:Building React and Vue Support for Tailwind UI by cageface on Wednesday April 14, 2021 @10:26AM (#26807521)
They specifically recommended using it in the documentation to solve exactly the problem you describe.
[ Parent | on HN ]