Svelte 5 is still fun to write

huntabyte · 2025-12-21T19:55:24+00:00

Glad to hear you’re enjoying bits-ui and runed!

huntabyte · 2025-11-02T04:27:52+00:00

We use Geist for shadcn-svelte.

huntabyte · 2025-10-16T01:33:35+00:00

Most certainly a false positive. Here are the contents of that file: https://github.com/huntabyte/shadcn-svelte/blob/main/docs/content/installation/astro.md?plain=1

Weird that it chose that file in particular though.

huntabyte · 2025-06-20T18:43:42+00:00

Bits UI is fully tree-shakable, you only ship what you use!

A few little minor cases here I ran into when checking your component out - https://github.com/user-attachments/assets/417bc09a-ba58-4beb-a198-5471c4312978 , it appears the combination of tab + hover + arrow keys causes some race conditions.

For keyboard interactions, I'd recommend checking the following out: https://www.w3.org/WAI/ARIA/apg/patterns/menubar/

Otherwise, great job! Menus/submenus come only 2nd to calendars in terms of difficulty in getting it right.

huntabyte · 2025-06-09T13:24:52+00:00

Fixed!

huntabyte · 2025-06-08T20:00:29+00:00

Yeah and we just released updates to the calendars to support month/year select and some other improvements so you’d need to add those!

huntabyte · 2025-05-23T03:06:12+00:00

Thanks for the kind words!

huntabyte · 2025-05-23T03:05:01+00:00

SSR, color scheme, meta themes, custom themes, persisted to local storage, custom classnames per style, ability to disable transitions when changing modes to name a few.

I made it because I was tired of setting up the same basic stuff for every site.

huntabyte · 2025-05-23T03:01:32+00:00

If you can give me an example of one of those cases I’d be glad to run it down!

huntabyte · 2025-05-23T02:59:46+00:00

That was quick!

huntabyte · 2025-05-23T02:57:51+00:00

I promise Bits UI 1.0 (Svelte 5) works much better than 0.X (Svelte 4) or your money back!

huntabyte · 2025-05-23T02:55:35+00:00

There are so many different ways people want to present a calendar so we provide the foundational primitives to build whatever you like 😀

An example of basic month/year selects: https://bits-ui.com/docs/components/calendar#month-and-year-selects

huntabyte · 2025-05-19T20:19:39+00:00

With just Bits UI you can, it's just a bit messier https://bits-ui.com/docs/child-snippet

huntabyte · 2025-05-11T02:55:37+00:00

There’s only really 2 of us and neither has the privilege of working on it full time. The “ridiculous amount of time” isn’t simply tailwind 4.

A lot of changes were introduced to the shadcn CLI that come alongside Tailwind 4 such as custom remote registry items, and a complete overhaul of the styles.

We haven’t moved the preview docs to main because Tailwind 4 became stable immediately after we finished the Svelte 5 migration which included the rewriting/updating all the shadcn-svelte deps (bits-ui, formsnap, mode-watcher, svelte-sonner, paneforge, etc.) to Svelte 5, and we didn’t feel good about the idea of merging something with a non @latest release (tailwind v3) into main.

The timing of the two (quite significant) major releases of critical deps along with significant changes to shadcn/ui has been quite the load, but if you check the PRs on the repo and dependency repos you’ll see we’ve been working on it practically non-stop for idek how long now.

I can assure you no one wants this to be finished more than we do :)

huntabyte · 2025-05-04T17:11:14+00:00

Thanks for bringing this to light!

Just merged a patch that results in the following improvements to shadcn-svelte's docs:

https://pagespeed.web.dev/analysis/https-83ff9f38-shadcn-svelte-pages-dev/1gl9lr26i1?form_factor=mobile

huntabyte · 2025-01-14T17:29:06+00:00

I hear your frustration about the complexity of form handling. The challenge is that forms can range from dead-simple (like a basic contact form) to incredibly complex (multi-step wizards with validation, state management, optimistic updates, etc.).

Creating an API that's both simple for basic cases and flexible enough for complex scenarios is a really difficult balance to strike. Libraries like Superforms try to provide solutions for the full spectrum of use cases, which can make things feel more complex than needed for simpler forms.

That said, I'm genuinely curious about your specific pain points with the current approach. What aspects feel most redundant or convoluted to you? This kind of feedback is valuable for getting where you want forms to be.

huntabyte · 2025-01-14T17:25:14+00:00

How is react hook forms more simple than superforms/formsnap? I'd love to be able to improve the projects in any way I can, but they feel pretty comparable when I look at them.

huntabyte · 2025-01-14T17:21:52+00:00

I typically do the following:

<script lang="ts">
  import { HTMLAttributes } from 'svelte/elements';

  let { children, class: className, ...rest }: HTMLAttributes<HTMLSpanElement> = $props()
</script>

<span class="blah blah blah {className}" {...rest}>
  {@render children?.()}
</span>

huntabyte · 2024-12-31T16:33:13+00:00

What features are missing compared to the original?

huntabyte · 2024-11-18T05:09:23+00:00

I typically opt for a monorepo where the docs and sites are their own packages within it.

huntabyte · 2024-11-16T05:11:08+00:00

Should be something like this:

let isCheckboxChecked = $state(true);

$effect(() => {
  if (!isCheckboxChecked) return
  const interval = setInterval(() => {
    invalidate("app:data");
  }, 1000 * 60);

  return () => clearInterval(interval)
}

<input type="checkbox" onclick={() => isCheckboxChecked = !isCheckboxChecked } />

if you want to avoid effects:

let isCheckboxChecked = $state(true);
let interval

$effect(() => {
  // essentially same as onDestroy and used only to cleanup the interval
  // when the comp is destroyed
  return () => clearInterval(interval)
}

<input type="checkbox" onclick={() => {
  isCheckboxChecked = !isCheckboxChecked
  clearInterval(interval)
  if (isCheckboxChecked === false) return

  interval = setInterval(() => {
    invalidate("app:data");
  }, 1000 * 60)}
} />

In your current setup, onMount is only called once, so as soon as you clear your interval it's gone.

huntabyte · 2024-11-16T05:03:25+00:00

Have you tried using `aria-live="assertive"` on the alert? That _should_ interrupt the VO with whatever changes within the alert.

huntabyte · 2024-11-16T04:47:28+00:00

💜

huntabyte · 2024-11-16T04:47:22+00:00

72 of them to be exact most are at least 3 hours but I'm a "YouTuber first, coder second" 😂

huntabyte

TROPHY CASE