fix(compat): map maxWidth to max-width namespace in v4 migration #19653
+2
−2
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.
Summary
In Tailwind CSS v4, the migration logic for v3 configurations incorrectly maps the
maxWidththeme key to the--container-*CSS variable namespace. This causes clashes with container query variables and breaks the primarymax-w-*utility design.This PR updates
OLD_TO_NEW_NAMESPACEto correctly mapmaxWidthtomax-width.Fixes #19555
Test Plan
Verified by updating existing core compatibility tests.
Execution command: