-
Hello! Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
Sure you can. But the effectiveness of the tailwind classes may depends on the usage of |
Beta Was this translation helpful? Give feedback.
-
Here is a similar situation with bootstrap tailwindlabs/tailwindcss#5080 |
Beta Was this translation helpful? Give feedback.
-
Thank you very much. Do you also recommend me to use tailwindCss prefix feature? |
Beta Was this translation helpful? Give feedback.
-
I have been using Tailwind + FUI for awhile now, they are playing nice to each others. You don't need a prefix for Tailwind if you don't want, but I suggest set corePlugins: {
preflight: false,
}, Although, there are few conflicts like this one: i.outline {
outline-style: none !important; /* To override `outline` in Tailwind` */
} If you ever use |
Beta Was this translation helpful? Give feedback.
Sure you can. But the effectiveness of the tailwind classes may depends on the usage of
!important
statement, because otherwise the FUI css selectors would possibly override the tailwind specificity. So if you want to use tailwind together with FUI, I suggest to respect the include order (first semantic.min.css, then tailwind.css) and to enable the !important feature in tailwind.If you don't want to combine the FUI classes with tailwind classes, this is most probably not needed.
So, if the tailwind classes are only used on non FUI components (which make use of the
ui
namespace class), you can just use both as they are as they should not interfere