[0.5] Move container component to a built-in plugin #418
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.
Resolves #256.
Prior to this PR, it was impossible to disable the
.containercomponent because it's sort of a special snowflake. It's not a utility class and doesn't support any of the variants that the rest of our utilities support; it's actually a component, and has different styles at different breakpoints.With the introduction of the new plugin system and the
@tailwind componentsdirective, it makes sense to inject the container styles into the components section of the user's stylesheet, and making the container a built-in plugin instead of a special-case hard-coded utility means it's now trivial to disable; you simply remove it from the plugin list:plugins: [ - require('tailwindcss/plugins/container')(), ],This is a breaking change so slated for 0.5.