Migrate tailwindcss to v4, and use it through vite plugin#1039
Closed
Migrate tailwindcss to v4, and use it through vite plugin#1039
Conversation
for more information, see https://pre-commit.ci
Member
Preview available
|
Member
Author
|
@hypha This will likely create conflicts with the sponsor PR because the colors were defined in the tailwind config. How would you like to move forward with this 🤗 |
Member
Author
|
Let's hold this until the sponsor PR gets merged! |
Member
Author
|
It is probably the safest option to hold this until after the conference, since it might affect existing and new pages. |
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
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.
The
hiddenclass no longer seems to work along with other classes that affect display.I had to use a workaround like this:
Also, there seems to be a new preferred way of configuration: inline configuration in CSS. I like it.
I had to tweak some components and pages to make this work, but I most likely missed something somewhere.
Closes #1038