Tailwind v4

[kuchta]

Hi guys,

I'm very excited about new Tailwind v4 developments and since I know there's no supports for plugins yet, do you think daisyui could be implemented with just the new "css-first" approach without using it as a plugin?

[saadeghi]

It's mentioned in the blog that plugins will be supported in the stable release (using the config file)

I'm also excited about getting rid of JS config file.
Hopefully importing plugins will also be possible using the CSS file. It will be great for daisyUI because daisyUI source files are CSS but I have to convert them all to CSS in JS during build time just so it can be imported in the JS file.

[kuchta]

Well, the problem with closed discussions is that they are not shown at the main page, so people wouldn't notice until they intentionally search for them and I actually wanted an answer from somebody who has practical experience with it...

[saadeghi]

I actually wanted an answer from somebody who has practical experience with it...

What's the question?

do you think daisyui could be implemented with just the new "css-first" approach without using it as a plugin?

I answered your question. Currently it's not implemented in the alpha version. There no API for it and there's no docs yet.

But this is the goal according to Adam's tweet:

[kuchta]

What's the question? Have somebody practical experience using (porting) daisyUI to the Tailwind v4 alpha?

If you had at least taken the time to understand the the blog post, you would't close the discussion, because you would understand that if as you say daisyUI is just css, than you probably don't need the new plugin API at all! You can just import daisyUI css and port all theme() functions calls to css variables and I don't know what else... That's why I'm asking, because I don't know daisyUI internals and it's interface with Tailwind to answer that, but you evidently don't know what this new version brings and your answers reflect that. Sorry to say that, but it's getting a little bit unbearable...

[saadeghi]

Have somebody practical experience using (porting) daisyUI to the Tailwind v4 alpha?

How can possibly anyone have practical experience of using a Tailwind CSS plugin when the creator of Tailwind CSS said it DOES NOT EXIST in the current alpha release?

we should leave this discussion open

the problem with closed discussion

you would't close the discussion

This is why you're a angry.

I've never seen anyone being this obsessive about a GitHub discussion so I don't know what to say at this point...

[kuchta]

If you understand the design of the new version, you wouldn't again and again talk about daisyUI as a plugin of Tailwind anymore. That's where the misunderstandings occur. If you don't know what to add to the discussion, it would be probably better not say anything and let it open for others to say samething actually usefull. I know this is you project and your repo, but you are not the only one here...