Repository navigation
Replies: 1 comment
|
Of course, Yes. But there is an important distinction between what Tailwind could implement and what fits its current extraction architecture. Tailwind currently treats source files largely as plain text rather than executing or semantically analyzing JavaScript. Its documentation explicitly says that string interpolation/concatenation is not understood, so: doesn't expose the complete max-lg:overflow-hidden token to the scanner. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Support dynamically constructed class names
It would be very useful if Tailwind could detect simple dynamically constructed class names at build time.
For example:
Currently, Tailwind may not generate "max-lg:overflow-hidden" because the full class name does not appear literally in the source.
I understand that fully supporting arbitrary dynamic strings may be impossible or expensive, but supporting simple statically analyzable cases like this could be very useful.
Would this be technically feasible for a future Tailwind version?
All reactions