Svelte
Remote queries in SvelteKit shed the .run() method — direct await query() now works in any context, reactive or not.
Remote queries work everywhere now. The .run() method is gone as of Kit 2.61.0; awaiting a query directly is the new universal API. The cache is shared across reactive and non-reactive subscribers, so an event handler that awaits a query deduplicates with components already subscribed to the same one. Live query instances also became async-iterable in this release.1
Remote forms gained a programmatic submit path. Kit 2.61.0 added a submit method directly on form remote function instances, and the enhance callback now receives the form instance.2 Form fields now accept numbers and booleans (not just strings), and unread validation issues on form functions surface a warning at dev time.3
A cross-site scripting fix shipped for SSR. Svelte 5.55.7 blocked an XSS vector in the hydratable path when user content was involved, hardened regex handling, and moved runtime properties to symbols.4
Async reactivity in Svelte 5 received sustained correctness fixes. Releases 5.55.6–5.55.9 addressed batch handling in {#await} blocks, stale derived resolution, eager-effect flushing in production, SSR context reapplication after errors, and obsolete async branch cancellation.5 The async rendering strategy switched from "blocking" to "merging" semantics.6
Route matching also saw fixes in Kit 2.61.1, correcting a regression where routes beginning and ending with a route group weren't matched correctly.7