Pouya Saadeghi
Pouya Saadeghi
Are you using npm version 6 or less? You can check by running `npm --version`
Can you please update every dependency (Parcel, daisyUI, Tailwind CSS, PostCSS) to the latest version and try again? I could not reproduce the issue with tailwindcss `3.2.2` (or even latest...
Can you please give me a repo so I can reproduce the issue?
I'm sure with default config, Parcel, Tailwind and DaisyUI work together without issue. However, I think your build process is making some modifications to the CSS. For example, there are...
> The issue lies somewhere in these changes: [v2.22.0...v2.23.0](https://github.com/saadeghi/daisyui/compare/v2.22.0...v2.23.0) This is the commit about table: https://github.com/saadeghi/daisyui/commit/4cedd563268847f01dfa8114ce0b1133e3b1e4b3 So basically I changed this: ```css .table { :where(:first-child) { /* style */ }...
I think the problem is from that part of your build process (I don't know what package or config is doing it) that is adding an `!important` rule. Here: ```...
@naps62 I'm glad the issue is gone. I still have no idea about the cause of issue but i'm sure it's not from daisyUI. daisyUI and Tailwind CSS do not...
>When building, Tailwind CSS will detect `!collapse` pattern and apply `!important` modifier. @maliut Good catch! This is the reason. This happens when we use `!anything` string in our markup and...
This is fixed in Tailwind CSS `3.2.7`
@arily it shouldn't be an issue. It must be fixed if it still exists. Which style is broken for you exactly? Which variable name is causing the issue?