-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable JIT support #4
Comments
It's actually a nice thing to have, because we're loading the full tailwindcss for each component, a few mb worth of css... We should generate a tailwind css compilation on real time by compiling on the browser, but i don't know if that is possible. |
Would this work? https://github.com/beyondcode/tailwindcss-jit-cdn edit: Appears to work for me, testing locally, with a simple html file and the included script tag. |
It looks exactly what we need, thank you! Maybe we should only enable this for components on version >= 2.0. What do you think @khatabwedaa ? |
Let take look 👀 . |
Just now I guess we can just add the script tag to the component page, it works: https://tailwindcomponents.com/component/card-carousel |
Awesome I will apply it for all v2 components Thanks Budy. |
Hey @maddog986, we added to the code base now you can use jit without including any script. |
Describe your Idea
JIT support would be nice. Having the ability to use peer-* on components opens a ton more possibilities for components.
Additional context
I built a simple carousel component, but can not submit due to it using peer-* styling. See it at https://play.tailwindcss.com/bzje1DhMN5
The text was updated successfully, but these errors were encountered: