the link has ) at the end, you might want to add a space at the end of the link

And what a *huge* help you've been! Cheers 🍻

Damn ive limiting myself to skeleton?? Shld i try out ur recommendation

​@@jaycool-lb9kjI also am using skeleton and feel like I made a bad decision in the long run. I have tried other libraries though. But shadcn looks very appealing.

Great to see you're not butthurt with competition. Your UI is great!

@@alexandrecosta2567 Chris has been great from the get-go. Ever since I started, with Radix Svelte, he reached out and has been super welcoming, never seeing it as competition, but instead as something that adds to the whole community, which in the end, it's what OSS is all about!

The entire Skeleton team is incredible, and I've learned a ton about managing projects, expectations, and more from Chris & Adrian from Skeleton ❤ you guys rock and I can't wait to see what Svelte 5 unlocks for you all!

@@alexandrecosta2567 One of the core maintainers of Skeleton (Adrian/CokaKoala) also maintains shadcn-svelte, bits UI, Melt UI's preprocessor, and helps me out with a ton of other projects. We're a close group ❤

Sua biblioteca é muito bonita, ainda está longe de todo seu potencial, mas é bom o suficiente para eu usar em meu próximo projeto, que se der certo, ficarei feliz em fazer alguma colaboração.

Would love to contribute to some more example screens and groupings of components down the track!

You're welcome! I've had a blast doing it!

My pleasure!

Thanks for the kind words!

My pleasure!

Yes please!

Thank you! 🙏🏻

Ideally soon. We want to release 1.0 before Svelte 5 is released so that major v2 will introduce Svelte 5 support, rather than having to make it a part of v1 with a divided ecosystem.

Thank you! Cheers!

What have you been doing?

I'm using `unovis`! You can snoop around the source code to see how they work, they are pretty decent from my limited use of them!

Arc!

I appreciate the kind words, but there are a lot of people who contribute to these projects and they wouldn't be close to where they are today without them ❤️ Even those who take the time to open issues and report bugs is a massive help!

Using it without typescript is on the roadmap 🫡

We actually don't dispatch an `on:change` for the slider but there is an open issue to add that feature. The docs for those events would fall under bits, which I'm actively looking for help in bringing up to speed!

I haven’t heard of that!

Noted!

It grows on you :)

Those stores will likely become reactive objects 😃, which makes it even more powerful!

Yes

No, its not for people who come from the react way of doing things. Components are in every framework for good reason, you get to offload the burden of maintaining intricate UI tests, accessibility research and functionality, etc.

and of course Bits UI already works with projects on Svelte 5. I don't want anybody to mislead ;)

They _should_ but won’t have guaranteed support until it’s stable :)

Hang out in the issues, look for ones with `help wanted`, find bugs, help others in the community via discord, there are lots of ways!

Not sure if you saw the “Preview” label beside the forms in the docs, which essentially means “Not Mature”, “Experimental”, “Still working out the details”. You can use the regular non-Form.X elements and accomplish what you need to accomplish.

@@Huntabyte I had not noticed the Preview tag on the form, sorry. And when you say non-Form.X elements, you probably mean e.g. the ... element? I'll try have a look at this again, only with the regular components. Dont get me wrong, apart from the Forms (which are in Preview, totally fair!), this library has worked flawlessly and very easy to use! Thank you for your contribution!

You bet!

Arc!

It's quite different, and whether the differences are good or bad is really up to you to determine. The first thing I want to mention is that these components can be used with SkeletonUI if you want to. This library is not meant to be a replacement for SkeletonUI and is meant for someone who wants more control and ownership of their components, which is not everyone. By taking control, you lose the ease of running `pnpm update` to get the latest stylistic updates, you strictly get the latest version of bits, which may fix bugs, add new functionality, etc. but as far as the styles go, it's up to you to update them. Skeleton is way ahead in terms of development, maturity, and overall support/maintenance, and is at a stable release, meaning you can be confident there aren't going to be breaking changes introduced until the next major, whereas bits/melt are still

@@Huntabyte thanks for the extensive answer!

Thanks for that! And you’d be correct about the bug scenario. However, we maintain the full stack, so it’s a bit different than if we were depending on another package we didn’t have ownership of. I’m able to identify within a couple minutes if something is related to shadcn, bits, or melt, and quickly reroute the ticket and (ideally) fix the issue! Regardless, I appreciate your opinion and agree that Skeleton UI is a great project! I always recommend it to peeps who have the same concerns you have!

Arc!

Different strokes for different folks!

@@Huntabyte After using it for a week it is not bad at all. I primary using it from now on. Love it ! that bind:open in everycomponent is the best exp!

I’m not sure if this is an insult or a compliment, but either way, I’ll take it! 🫡

🤷🏻‍♂️

It doesn’t say anywhere in that quote that it’s a bad thing. Native HTML elements while great are limiting and inconsistent across browsers and platforms. There’s a reason W3C Aria Patterns exist 👍

Slightly though, init.

Then Melt-UI is too low level for you, go up the stack and use bits or shad. Its like complaining that you don't like wasm because JavaScript should be readable.

Thanks for the insight!