Allow users to block generation of certain utilities #9812
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.
Sometimes you're generating classes that you don't want to generate because they're matched in your content.
For example, we have a
container
class. If your content has the wordcontainer
in it somewhere that's not meant to be an actual class we would still generate it.Another case is you have a class like
collapse
that is shared by Tailwind CSS and another framework that you're using and the behavior between the two is different.Historically, we've recommended disabling the core plugin that generates these classes and then either adding custom CSS or a plugin to your own config that generates the classes you want.
For example, to disable the
collapse
utility you would add this to your config:However, this solution is less than ideal because the resulting CSS will be in a different order and you have to replicate most of the core plugin in your own config file.
Here we're introducing a new
blocklist
option that allows you to selectively disable generation of utilities that you do not want. For the situation above, with thecollapse
utility, you would now add this to your config:The utilities are matched by their exact class names. This means that if you want to block
hover:mx-auto
you would addhover:mx-auto
to the blocklist. Simply includingmx-auto
on it's own will not prevent variants from being generated if they are matched.