Tailwind CSS utility generation vs runtime‑composed class names: safelist or source refactor
Goal Ensure that every utility class needed at runtime appears in the production CSS even when class names are assembled dynamically, such as via string concatenation in JavaScript templates. Constraints Tailwind’s content scan only detects literal class names in configured files; dynamically built strings are ignored unless explicitly safelisted. Adding saf
tailwindcss
postcss