Conduitry

Are you using Svelte 4 or Svelte 5? https://svelte-5-preview.vercel.app/docs/breaking-changes#other-breaking-changes-img-src-and-html-hydration-mismatches-are-not-repaired This is an intended breaking change in v5.

IMO the types _should_ fail - Previously, whenever people opened issues about "why do the types fail when my `onMount` function returns a promise", our argument was that that was...

I'm having a hard time seeing when it would be an unpleasant surprise for someone that their `reroute` hook is being run, even if for some reason they weren't expecting...

Alternatively, we could expose a `proxify` function (name TBD) from the Svelte runtime, which wouldn't require any compiler changes. You would then do `$derived(proxify(whatever))` when you need a mutable reactive...

A significant argument against a rune in my view is the inability to use it in a SvelteKit `load` functions. The name `proxify` does make me uncomfortable because it exposes...

See also #6536, including some of the comments there from this year. It does sound like there is some issue that people have been having more recently with this, but...

It's for screen readers. https://svelte.dev/docs/kit/accessibility#Route-announcements

SvelteKit does not yet use hydratables for remote functions - that is coming soon in #14872. We should keep the warning at least until then.

Please provide a complete and minimal reproduction, not just a code snippet referring to other parts of your codebase that aren't included.

I don't know whether we have an official stance on this, but adding types for an experimental feature that's only available in one of the three big browser engines feels...