Would you like to create headless components for svelte ?

[mitya-borodin]

No description provided.

[RobinMalfait]

Hey! Thank you for your suggestion!
Much appreciated! 🙏

We are first focusing on React & Vue components, so I can't give you a good answer on this one.
Maybe in the future!

[shajidhasan]

Any update?

[gmonarque]

Support for svelte would be so cool!

[allochi]

Tailwind has a lot of love and attention from Svelte developers, couldn't you open some guidelines for us to help you add one?

[chumleesockson]

It must be getting closer to the point where Svelte support will be considered. Maybe once Sveltekit is properly released?

[bugproof]

@chumleesockson
yup still in beta https://github.com/sveltejs/kit/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0+sort%3Aupdated-desc
someone has started the work https://github.com/mattjennings/headlessui-svelte but it supports only 1 component(switch) looking at the readme and the library seems abandoned.

[benmccann]

A Svelte implementation has been created here: https://github.com/rgossiaux/svelte-headlessui

[alec-c4]

@RobinMalfait it would be nice if @tailwindlabs can join their forces with author of https://github.com/rgossiaux/svelte-headlessui

[eliasdefaria]

Would love for Svelte support! Currently using -> https://github.com/rgossiaux/svelte-headlessui

[akbog]

Has there been any headway in implementing Svelte Support?

[rohanrajpal]

A new headless UI library is out with a much more Sveltier way of doing things!
https://github.com/captaincodeman/svelte-headlessui

[eliasdefaria]

A new headless UI library is out with a much more Sveltier way of doing things! https://github.com/captaincodeman/svelte-headlessui

Niiiice. Will give this a go

[noxware]

+1 to support Svelte

[greendesertsnow]

Svelte support please

[jiri]

Rather than just bumping this thread, I'd like to provide a more in-depth argument for first-class Svelte support.

There has recently been the 1.0 release of SvelteKit, with libraries such as Auth.js (formerly NextAuth) adopting SvelteKit as the first framework other than Next.js. With companies like Vercel showing support for Svelte, I think it's time for HeadlessUI to add official support as well.

While I understand that this would be a lot of work and HeadlessUI is an open-source library, it's a somewhat necessary part of TailwindUI, which is a service users pay for (and not a small amount IMO). Until Svelte support is added, at least for me personally it doesn't make sense to pay for TailwindUI.

[cupcakearmy]

I agree with @jiri
Also maybe one could talk to @CaptainCodeman as they already made the amazing efford to bring it to svelte, so it's just a matter of brining on the package, and then of course the work mantaining it.

[jasongitmail]

As someone who both purchased Tailwind UI personally & had my former company buy a Tailwind UI Team license, this creates a bit of a quandary, because we use SvelteKit now for new projects. I know HeadlessUI is a prerequisite step in that direction.

Would love clarity on how the community can help contribute to official Headless UI for Svelte support--requirements to be met to merge PRs for official support, need a suggestion of a Svelte contractor, etc? Thx!

[eliasdefaria]

I'd also be very willing to contribute to an official Svelte port. Svelte is on the rise :)

[CaptainCodeman]

I agree with @jiri Also maybe one could talk to @CaptainCodeman as they already made the amazing efford to bring it to svelte, so it's just a matter of brining on the package, and then of course the work mantaining it.

My focus was on making the bundle size as small as possible and exploring an alternative "sveltier" approach (stores + actions instead of wrapper components and slots, which help with reducing the bundle size and I find simpler to consume).

I think the approach works but it's really missing thorough unit testing right now which I have on my TODO list (just been busy with work projects). Ideally the testing system would be made less framework specific to make correctness and consistency across all implementations easier.

[mdkq]

+1

[wesharper]

Just started a new project with SvelteKit and realizing how heavy a lift it is to do certain things using TailwindUI without svelte primitives. I was naive in thinking that the html versions of components would be easily reproducible. It's fine for some things, but for interactive elements like comboboxes and for transitions, finding the right combination of third-party libraries and custom work vs just going down a different road altogether has been a struggle.

[rohanrajpal]

Just started a new project with SvelteKit and realizing how heavy a lift it is to do certain things using TailwindUI without svelte primitives. I was naive in thinking that the html versions of components would be easily reproducible. It's fine for some things, but for interactive elements like comboboxes and for transitions, finding the right combination of third-party libraries and custom work vs just going down a different road altogether has been a struggle.

I have given up on Tailwind UI for Svelte, tho its fair, they have a lot on their plate and might get to this sometime later.

That being said, have really good hopes from Melt UI: https://github.com/melt-ui/melt-ui

It's the closest to a complete headless library

[wesharper]

Nice, thanks! I'll take a look.