svelte-headlessui VS svelte-headlessui

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.

The component's come pre-styled. Styles can be overridden by tailwind classes, and here's a guide for that on the docs! If you want to use components that don't come pre-styled, I would suggest using something like Svelte Headless UI.

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.

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

You mention YAGNI, but I think the bigger blocker is "Don't reinvent the wheel" - which I think is the most misunderstood bit of programming advice out there. In my SvelteKit app, I am not using a "UI Framework" that provides components to me. I don't need to. Svelte is simple enough that I can build almost anything myself. I've looked at Skeleton's source code, and their components on average are not better than versions I have rolled myself. There are a few cases where it's better to use a framework. Sliders, for instance, have a lot of edge cases. So I use Swiper for carousels. But even then, I could build a working basic slider (that doesn't address the numerous edge cases) myself in an hour. The other case is Headless UI but even there, I disagree with how he implemented some things and it's possible to roll your own Svelte Headless UI just from Tailwind's source.

I've been using https://github.com/captaincodeman/svelte-headlessui/ since previous with react I was using headlessui w/ tailwid.

I've also seen this alternative library utilising svelte use:action directive rather than components.