component-template VS svelte-headlessui

Reason I'm asking is that the official component template has a build step that compiles it to pure js. But I just tried publishing it with no build step (so literally just button.svelte, index.mjs and package.json and it seems to work fine.

But what would it be like to build your own Svelte component library? Fortunately, there are several templates that you could start with, like the official template provided by Svelte and Svelte 3 Component Template, which are considered the go-to for building your own component library.

My question is: is there a good up-to-date Tailwind, Svelte, Storybook template out there? The one on Github is pretty old and was abandoned 5+ months ago. With the pace of change, I'm worried I'd bump into legacy bugs. I'm confused as to where to start because Svelte has an official component-template but its 10 months old. Also, which bundler is the best for a newbie? Lastly, should I use svelte-add or is there a more stable solution out there with support for Storybook?

The official component template still has an open issue pertaining typescript support, and there's several templates linked there. Given that time is a rare resource, and given that I frankly don't trust myself to make the right decision here up-front, I'd be interested in your thoughts and experiences. Are there trade-offs in the available TS templates? Or does one of them basically tick all the boxes already? If so, why is there no endorsed official TS template?

Svelte Headless UI is a library of unstyled, accessible UI components, inspired by Tailwind's Headless UI. It gives you all the interactivity without enforcing styles, allowing you to design the components exactly the way you want. With Svelte’s reactivity and this library's flexibility, building complex UI interactions has never been easier. Github repository →

GitHub: 1.8k stars License: MIT

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.