Closed luizkowalski closed 1 year ago
Hi there :wave: Thanks for raising the issue, could you please let me know which versions of Tailwind and DaisyUI you are using?
I'll try to reproduce the issue later today.
daisyUI: 2.25.0
tailwindcss: 3.1.8
Sorry for not responding back then, IIRC I tried to reproduce it in a minimal setup but wasn't able to replicate the issue.
Please open a new issue if a similar problem still occurs in the current release.
Edit: I found my old repo trying to replicate this: This issue can be worked around by specifying a prefix for the plugin:
require("@catppuccin/tailwindcss")({ prefix: "ctp" }),
So bg-red
won't be overridden by Catppuccin red, and won't lose its shades. bg-ctp-red
will be the Catppuccin red instead.
Finally managed to fix this for good, shades for default colors such as red
, green
, blue
, etc. should work now, while keeping bg-red
as the Catppuccin red, even when the prefix isn't specified.
Apologies for the lack of a response for such a long time again.
hey!
I have an app running with DaisyUI and a couple of custom styles like this:
as soon as I add the plugin, without any config, just
require("@catppuccin/tailwindcss")
, I start to see errors like thisring-blue-400
is a class from tailwind and now it can't be found. It happens to a number of other classes as well, likefrom-pink-400
,text-blue-900
, etc.