Thank you for these clear directions. I have been trying to attach Tailwind to Quasar components (ex q-input) that already have their own CSS. So far the Quasar CSS has been overwriting most of the Tailwind CSS. Do you have suggestions on how to reverse this? (my Tailwind classes are prefixed with tw-)
Thanks for your question. I’m currently sticking to using Quasar’s CSS in my own project rather than trying to fight with the framework as I don’t think there currently is a way to fix the conflicts you described.
I mainly wrote that for fun and would wait until/if this is fixed before trying to use Tailwind & Quasar together on a production app without running into these issues.
There’s an open issue about this on Quasar’s Github page.
I hope they are able to “fix” this as I would love to be able to use either or both options.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for these clear directions. I have been trying to attach Tailwind to Quasar components (ex q-input) that already have their own CSS. So far the Quasar CSS has been overwriting most of the Tailwind CSS. Do you have suggestions on how to reverse this? (my Tailwind classes are prefixed with tw-)
Hi LinnaeK 👋,
Thanks for your question. I’m currently sticking to using Quasar’s CSS in my own project rather than trying to fight with the framework as I don’t think there currently is a way to fix the conflicts you described.
I mainly wrote that for fun and would wait until/if this is fixed before trying to use Tailwind & Quasar together on a production app without running into these issues.
There’s an open issue about this on Quasar’s Github page.
I hope they are able to “fix” this as I would love to be able to use either or both options.