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 adds a new
2xl
breakpoint behind an experimentaladditionalBreakpoint
flag.Adding bigger breakpoints is a really common Tailwind customization, and as devices continue to get bigger with higher resolution, I think we're going to eventually wish we had something a little bigger than 1280. Bootstrap is even adding a 1400px breakpoint in Bootstrap 5, so we're not alone in thinking an additional large breakpoint would be helpful.
I considered a few different sizes for different reasons:
I settled on 1536px after looking at some Google Analytics results with @reinink for multiple sites we both run and noticing that it was a surprisingly popular resolution (more popular than 1440px in a lot of cases). It appears to be very common for Windows machines, and since it's also the exact resolution I run on my 16" MBP, and a nice even 256px jump over our 1280 breakpoint, it felt like a great choice. Wide enough to let you make significant changes vs a 1280 breakpoint, but not so wide that you can't trigger it on large laptop displays.
Going to keep this experimental for now in case any issues come up with the name
2xl
, because it needs to be escaped in a weird way and I worry there may be some tooling out there that doesn't play nice with it, so lets test it for a bit to double check we're safe.This increases the default file size significantly, but whatever, you should be removing unused styles anyways. I'm going to work on a PR for a "lite" mode with a significantly reduced bundle size soon for people who have to use Tailwind from a CDN and don't want to serve a large file.