Conversation
Allows for usage of min/max width with regular tailwind units
|
|
This was referenced Mar 12, 2026
Merged
Contributor
Author
|
Update Changelog and (temporarily) point dependent PRs to that one for better diffs |
kylebonnici
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Explanation
Since 3.4.0 Tailwind allows for usage of min/max width with regular tailwind units.
Problems encountered
Tailwind versions superior to
3.4.14create an issue with types (and sometimes package import in general) inscripts/esbuild-renderer.ts.This will probably be investigated later so that an upgrade to Tailwind 4 can be achieved.
In the meantime, version
3.4.14it is.