feat: unocss support #1666
Closed
feat: unocss support #1666
Conversation
This file contains 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
ineshbose
commented
Apr 14, 2024
ineshbose
force-pushed
the
feat/unocss-support
branch
from
019c78e
to
5cde106
Compare
|
I can't wait for PR to be ready! |
|
Closing this PR for now as I'm unable to work on this (plus recovering from a surgery in hospital). 🙁 If anyone wants to give it a go and pick up from this point, please do! ❤️ |
|
is there any updates on this feature? |
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 is just a work in progress, proof of concept to see if we can easily switch out TailwindCSS for UnoCSS if developers want this (the demand is duly noted)
🔗 Linked issue
❓ Type of change
📚 Description
Builds on top of #1665 where we also encapsulate installation of Tailwind...
📝 Checklist