Open
Conversation
Member
|
Haha, yeah, all my projects are broken at the moment because of this. 😅 I actually figured out the upgrade path this morning, so I'll do a proper fix real quick. But thanks anyway! |
Member
|
(Another lesson to pin all dependencies I guess…) |
Contributor
Author
|
Excellent, even better! |
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
2 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.
Tailwind v4 released a week or two ago and it broke the site CSS when we rolled out the converter list. At least for now, the quickest fix is to just point to a v3 release of the Tailwind CLI.