SvelteKit 3.0 release candidate introduces remote functions, a type‑safe mechanism that lets individual page components retrieve data from the server without reloading the entire page.

SvelteKit, a framework built on the Svelte component library, has positioned itself as a lighter alternative to Next.js, a popular React‑based framework. A recent benchmark showed SvelteKit’s server‑side rendering payload to be about three times smaller than Next.js for comparable pages.

Remote functions compile to a lightweight client‑side wrapper that calls a server endpoint directly from a component. The server validates the request, queries data, and returns serialized results, eliminating the need for custom routing or additional boilerplate. The feature is experimental since SvelteKit 2.27 and will be included in the upcoming v3 release if remaining issues are resolved.

Vercel, which maintains both SvelteKit and Next.js, notes that Next.js Server Functions provide similar client‑to‑server calls but are oriented toward mutations rather than queries. Scott Tolinski said the code can run anywhere within a component, and Simon Holthausen described remote functions as a rethink of traditional RPCs.

Tolinski explained that a component can import a query or mutation as a function and call it directly, enabling a footer component to refresh its data without affecting the rest of the page. The broader impact of remote functions will depend on performance and stability after the official release.