[WIP] Upgrade to Tailwind v4 #229
Closed
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
|
Closing this pull request as this was done in #292. |
|
Thanks for your effort though @ylynfatt! |
|
No problem. Sorry I wasn't able to complete it, but I'm happy a member of the Filament team was able to complete it. |
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.
This is still a WIP, but I began working on the changes.
It seems for now Filament have pinned v3 of their package to v3 of Tailwind. See recent pull request by the Filament team. As such, I had to make a few adjustments to how the filament CSS was imported (some not seen in this pull request). So for example, some modifications were made to
vendor/filament/filament/resources/css/theme.cssandvendor/filament/filament/resources/css/index.cssin order for thedashboard/theme.cssin Cachet core to compile properly.