Experimental support for variant grouping #8405
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a highly requested feature for grouping variants together. https://twitter.com/adamwathan/status/1461519820411789314
Also keep in mind that Tailwind CSS is a build-time tool and not a runtime tool. We are also not rewriting your source files which is why there are some downsides in bundle size.
The syntax allows you to group utilities for a given variant. Since these classes actually end up in your HTML, it means that you can't use spaces, instead you can use a
,
to separate your utilities.Before:
After:
You can nest variants and apply multiple variants at the same time.
If you are brave, while not recommended, you can also combine all crazy variations of it at the same time...
Input:
Generates 😅:
This feature is currently experimental and doesn't have proper intellisense / prettier sorting support. You can try it using the
insiders
build and by enabling the feature flag: