> This should be called "Don't use Tailwind in a React library for a design system" That's true. > as this really has nothing to do with Tailwind Well.. it h

> This should be called "Don't use Tailwind in a React library for a design system" That's true. > as this really has nothing to do with Tailwind Well.. it has to do with using Tailwind with React for a design system. :) He does mention that @apply doesn't fix the problems he mentions, which is what Tailwind suggests as the solution for abstraction when you don't use a component framework: https://tailwindcss.com/#component-driven https://tailwindcss.com/#component-driven (scroll down to "Not into component frameworks?")