Allow enabling/disabling modules and specifying variants from config file #233
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.
Still WIP
This PR does a bunch of stuff:
Makes module names more consistent so each generator matches the name we want to expose to the user for that module
Adds a new
moduleskey to the config file where you can customize how Tailwind generates each moduleMissing keys in the config now use the default values for those keys; this was already happening in some places but it's now consistent
Allows specifying the generated variants for a given module in the config file, including not generating responsive variants for a given module if desired:
Allows disabling a module:
Moves hard-coded decisions about which utilities get which variants by default into the default config file instead
Still to do:
generateUtilitiesplugin to make it easier to write some tests for the new configuration features