Tailwind v4 Oxide

[lil5]

With the news on tailwind v4 https://tailwindcss.com/blog/tailwindcss-v4-alpha
How will this impact daisy ui?
Will you still need postcss?

[saadeghi]

Post CSS is not a dependency of daisyUI anyway.

There current alpha release doesn't support plugins yet (as mentioned in the blog post) so we don't know yet how's the API going to be.

According to the blog post, it will still be possible to use plugins in using the JS config file as before (in the stable version)

And according to Adam's Twitter, it will also be possible to use plugins directly in the CSS file. The syntax probably will be @import "daisyui"

And hopefully (we don't know yet) it will be possible to import CSS files instead of CSS in JS. If so, it will be a big favor for daisyUI because currently the source files are CSS but we have to convert them to CSS in JS to be able to be imported to Tailwind because the current API only accepts CSS in JS.

There's no documents or news about how the API for plugins is going to be so we don't know yet. And in the current alpha release plugins are not supported.

I'm excited about Tailwind 4 and moving forward to use the CSS approach and it will also be the same direction daisyUI is going to move forward.

Let me know if you have any questions

[ajaypatelaj]

The syntax probably will be @import "daisyui"
🤞, I would be great if works like that

Hopefully (we don't know yet) it will be possible to import CSS files instead of CSS in JS.

That's correct, as per Adam's post the first point of his roadmap is to support tailwind.config.js. If this comes true, we can still use the DasiyUI existing plugin mechanism, Right?
The reason behind asking this question is that we've already started our project with DaiyUI and would like to be optimistic for DaisyUI to continue using it.

And hopefully (we don't know yet) it will be possible to import CSS files instead of CSS in JS. If so, it will be a big favor for daisyUI because currently the source files are CSS but we have to convert them to CSS in JS to be able to be imported to Tailwind because the current API only accepts CSS in JS.
Right, currently DasiyUI creates CSS first and converts them to JS files so that can be used as the TailwindCSS plugin.

As per Adams's vision for v4 CSS First Configuration, Let's assume that TailwindCSS v4 provides an API to use Plugin as CSS, will be provided support for that?
How that would be possible? (I can understand that it's too early a question for now)
What would be your planning and vision for the same for DaisyUI?

Apologies for being a bit insistent, but we strongly prefer to continue utilizing DaisyUI. However, it would greatly benefit both the DaisyUI community and yourself if you could offer ongoing support for future updates and ensure compatibility for those integrating it into their existing projects.

[saadeghi]

Let's assume that TailwindCSS v4 provides an API to use Plugin as CSS, will be provided support for that?

Yes, of course.

How that would be possible?

Currently I have as much information as anyone else. They didn't made the API or V4 docs public yet so we don't know how it's going to work. Whatever it is going to be, daisyUI will go with the same direction as Tailwind CSS.

What would be your planning and vision for the same for DaisyUI?

Yes, of course.

[oneezy]

i have tw v4 example setup so daisy ui devs can start porting over (very easy!)

i already commented on another discussion so i'll just link it here:
#2894 (comment)