Incompatibility between Tailwind v4 and DaisyUI in Astro Project

[arthurgubaidullin]

Astro Info

Astro                    v5.2.5
Node                     v22.12.0
System                   Linux (arm64)
Package Manager          npm
Output                   server
Adapter                  @astrojs/cloudflare
Integrations             none

Clipboard command not found!
Please manually copy the text above.

If this issue only occurs in one browser, which browser is a problem?

Any

Describe the Bug

After updating TailwindCSS to version 4 in the Astro project, DaisyUI no longer functions as expected. Component styling and utility classes provided by DaisyUI are either missing or incorrectly applied, breaking the UI.

What's the expected result?

I expect the update to not break anything.

Link to Minimal Reproducible Example

None

Participation

• I am willing to submit a pull request for this issue.

[rice-cracker-dev]

This isn't an Astro issue, the current version of DaisyUI only supports TailwindCSS v3.
However, there is a beta for the next version of DaisyUI which supports TailwindCSS v4 here: https://v5.daisyui.com

Keep in mind that there will be breaking changes as TailwindCSS is now using a CSS-only config.

[arthurgubaidullin]

Dear Maintainers,

I noticed that a breaking change was included in the most recent release, and I wanted to ask for some clarification. Could you please explain why this breaking change was categorized as a minor version update, rather than a major one?

Thank you for your time and your hard work on the project. Looking forward to your response.

[florian-lefebvre]

Hi, the integration update is a major since it's deprecated. The CLI update is a patch because the goal is to reflect the latest version of Tailwind. For the reminder, astro add tailwind only acts as a convenience for setting the intergation manually so there's no breaking change