Closed marshallswain closed 2 years ago
Thanks for the workaround @marshallswain π
Honestly Windi has been a huge problem for me. Their transform
API is super-buggy and never works as intended to transform plugins π₯² I'm so tired of opening new issues there...
If this workaround does the job, I can replace this in daisyUI docs π€·ββοΈ
This has been my experience as well. Their plug-in API is great, but is buggy when transforming tailwind-intended plugins.
I intend to explore the components more this weekend to see what doesn't work, but initial support is looking good with this workaround.
Related to this: I tried using Windi with daisyui - and some hover states are weird - even after the colours workaround.
This is the html from the daisyui site, and the light theme selected - powered by Windi. The "change theme" button should not be this colour.
Tailwind works correctly here.
I would suggest using Tailwind 3 instead. It's faster and JIT mode is enabled by default. I think I should close this because Windi's transform function is not behaving as expected and I can't do anything about it π€·ββοΈ
The Daisy colors aren't getting auto-installed by calling
transform('daisyui')
. As a workaround, I can do the following:Note that I don't have o install the
colors/windi
file to get the colors to work.I've tried to debug what's going on. I was able to verify that the
isTailwindInstalled !== false
code at the bottom of index.js runs. I couldn't do any further debugging tonight.