Tailwind: Fixed 'screen' -> 'screens' bug to properly adopt breakpoints. #3119
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.
Description
Someone (me) can't type properly and as a consequence our tailwind-config did not properly adopt the 'screens' config for breakpoints added 1+ year ago.
Why is this a breaking change?
Every project using tailwind will have used these values for their breakpoints before. By changing to our breakpoints with this change,
sm
will now be480px
and2xl
will be1440px
.2xl
change since one seldom use that breakpointsm
-change. In most cases this will not actually require a code update on their side, but will need each project to check that everything still looks as it should. Worst case scenario might be elements not wrapping properly 🤔 The change itself is only a 160px difference, so the possibility for actual breaking changes are few.Nice thing about the update is that each project can override this themselves by just adding two lines of code in their config. This allows them to update to next major without actually using this update. Since each project using tailwind already have a config, this will be quite easy to adopt.