SvelteKit 2.61 breaks remote functions, adds live queries

WHY IT MATTERS: SvelteKit shipped four minor versions in June that fundamentally change how remote functions and forms behave. If your team is using SvelteKit's remote functions for server communication, three breaking changes will break your build until you refactor. The updates also introduce a new real-time data primitive that could replace manual polling or WebSocket plumbing in Svelte apps, while template-level declarations in Svelte 5.56.0 reduce component boilerplate.

WHAT CHANGED: Remote queries lost their .run() method entirely in 2.61.0; you must now use await query() directly everywhere including event handlers and module scope. Enhance callbacks no longer receive a destructured object with form, data, and submit; they now receive a copy of the form remote function instance, which exposes its own programmatic submit() API. The requested() helper now requires a limit argument and yields { arg, query } tuples instead of returning the validated argument directly, though it also gains query.batch() support for inspecting batched requests. On the additive side, query.live() debuted as an async-iterable way to subscribe to long-lived server data, and remote queries gained shared cache deduplication across reactive and non-reactive consumers. Svelte 5.56.0 now allows variable declarations directly in markup templates, and the language-tools stack upgraded to TypeScript 6.0 support.

WHAT TO WATCH: Audit your remote function usage before bumping SvelteKit past 2.57.0. Search for .run(), requested() calls without limit, and enhance callbacks that destructure form or submit. If you need real-time server data, evaluate query.live() as a replacement for manual fetch loops. The SvelteKit remote forms API is still stabilizing, so expect more breaking changes in the next few releases.