Fix arbitrary shorthand syntax to use v3 syntax instead of v4 syntax #2233
Conversation
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
The `(` and `)` syntax was introduced in Tailwind CSS v4. This blog post is about Tailwind CSS v3.3 where we introduced the `foo-[…]` shorthand.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
philipp-spiess
approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes an issue where in the Tailwind CSS v3.3 blog post, we were using Tailwind CSS v4 variable shorthand syntax.
Fixes: #2232