svelte-headlessui VS daisyui

As a side note, my project was the first to be published under the name svelte-headlessui and is both more popular and more complete than the other project. I don't know why the other guy picked an identical name but it drives me a little nuts because of how unnecessarily confusing it is.

There is an unofficial Svelte port here but it doesn’t appear to be maintained so there may be a better option… that said there are a ton of better options if you want to use Tailwind with Svelte.

This and passing styles to slots, are biggest bottlenecks in wrapping components (your use case) and creating headless components (see headless ui).

Headless UI as in svelte-headlessui?

Svelte Headless UI should get some new PRs merged soon based on some comments u/ryangossiaux posted in the repo less than a week ago. He stepped away from the project for a bit after putting in a tremendous amount of work into it, and as someone who has used his library alongside Tailwinds UI on a number of projects, I’m super thankful for what he’s managed to do, and I hope that more people from the community will help support the project.

Just in case you haven't seen it, I ported Headless UI to Svelte recently: https://github.com/rgossiaux/svelte-headlessui

About two weeks into my first project I did purchase Tailwind UI. It is a massively useful resource, and I use it several times a week. It is a great reference tool, and is being actively added to. I have definitely recovered my initial investment in time saved. If you're using React or Vue, it is a no brainer - support if first class (along with Headless UI). I actually pivoted to SvelteKit, and started using the Tailwind UI HTML components until recently when this dropped: https://github.com/rgossiaux/svelte-headlessui. I now start with the React component.

Sure, it's here. Unfortunately I'm still writing independent documentation--and as we know from the survey, documentation is the most important part of a library :)

While I have experience with Tailwind and frontend development, I don’t really have the patience to use it. I usually end up using something like Mantine, which is a complete component library UI kit, or Daisy UI, which is a component library built on top of Tailwind. Shadcn/ui is quite similar to Daisy in this sense, but being able to customize the individual components, since they get installed to your components folder, made development more streamlined and more customizable. On top of that being able to change my components style with natural language thanks to v0 made development super easy and fast. Shadcn may be too minimalist of a style for some, but thanks to all the components being local, you can customize them quickly and easily!

https://daisyui.com is a really great middle ground—you can move as fast as you would in Bulma, then drop down into the weeds with TW if you need it.

If you're looking for grab and go components, Daisy UI or Flowbite might be more your speed, I've used both with minimal headache.

https://daisyui.com/

This guide is tailored for front-end developers looking to explore the smooth integration of DaisyUI's stylish components, Alpine.js's minimalist reactive framework, and the straightforward back-end capabilities of Codehooks.io.

Others:

  - https://daisyui.com/

🔍 Site ⭐ GitHub