LoginSign Up
← Back to all sparks
S

Svelte

DEVOPS
Velocity3.8

Cybernetically enhanced web apps framework

svelte.dev ↗

SvelteKit 3 steps into preview, and its config pivot is already shipping in the stable line.

sveltekit-3remote-functionsbuild-configmonthly-digesttypescriptmcp
◆Current state
Svelte publishes one digest per month rather than per-release notes, so each entry compresses a month of framework and SvelteKit work into a single post. The through-line for most of 2026 is SvelteKit's remote functions maturing, with .live() queries, batched requests, form validity booleans and typed fields, alongside steadier compiler work in Svelte 5.x. As of August the first SvelteKit 3 @next builds are out, following thirteen preview versions shipped in July alone.
◆Where it's heading
SvelteKit 3 is being landed in pieces before it is named: config moving into vite.config.js, explicit environment variables replacing $env/* modules, tracing leaving the experimental namespace, and shallow routing folded into goto. The stable 2.x line carries each change first, so the major version reads as a consolidation of already-shipped previews rather than a rewrite. Svelte itself continues on a slower, less disruptive track, filling in error boundaries, TrustedHTML and context APIs.
◆Prediction
Expect the @next line to keep absorbing the remaining experimental previews, with explicit environment variables and the service worker modules the obvious next promotions, before a stable SvelteKit 3. The entries give no release date, so timing beyond continued previews is unclear.

◆Recent moves

  1. 9d ago

    SvelteKit 3 opens its preview line with 13 @next releases

    ⚡ SPARK

    The first SvelteKit 3 @next builds arrive after thirteen preview versions in July, previewing $app/manifest and $app/service-worker modules, better service worker typing, tracing promoted out of the experimental namespace, and shallow routing folded into goto. This is the point where the Kit 3 arc stops being scattered 2.x features and becomes a named prerelease. The stable line keeps moving in parallel with submitted on remote forms and a new home for defineEnvVars.

    View source ↗
  2. 1mo ago

    SvelteKit config moves into vite.config.js

    SvelteKit config can now live directly inside vite.config.js, making svelte.config.js optional, and explicit environment variables get a first preview as the eventual replacement for $env/* modules. Both ship in the 2.x line while previewing how Kit 3 will require configuration to be structured. The language tools and the sv CLI also caught up with the {const ...} declaration tag, putting the toolchain back in sync.

    View source ↗
  3. 2mo ago

    Remote functions gain .live() queries and batched requests

    Remote functions gain a .live(...) query for real-time server data, form submit starts returning a validity boolean, and requested(...) takes a breaking change that now requires limit and yields { arg, query } entries. Remote functions are the fastest-moving part of SvelteKit, and breaking their API mid-2.x signals the shape is still being settled ahead of Kit 3. Batch request support through query.batch(...) lands alongside.

    View source ↗
  4. 3mo ago

    TypeScript 6.0 support and richer remote function transport

    TypeScript 6.0 support lands, form fields gain field.as(type, value) defaults to cut boilerplate on pre-populated forms, and remote function transport moves to hydratable so queries can return richer data types. Community plugins arrive in the Svelte CLI as an experimental release. Steady widening along the same remote-functions and tooling axes the following months continue.

    View source ↗
  5. 4mo ago

    Svelte MCP gets OpenCode packaging; best practices guide lands

    A best practices guide joins the docs, the Svelte MCP becomes easier to adopt through the official OpenCode package with generated config in sv's .opencode/ folder, and svelte.config.js gains functions for setting css, runes and customElement from one source. Server-side error boundaries land in SvelteKit. The MCP packaging is the thread worth noting, since it meets coding agents on tooling they already run rather than building a separate integration.

    View source ↗
  6. 5mo ago

    Server-side error boundaries and TrustedHTML support land

    Error boundaries begin working on the server, {@html} expressions accept TrustedHTML, createContext works when instantiating components programmatically, and comments are permitted inside HTML tags. This is core compiler work rather than SvelteKit surface, closing correctness gaps in Svelte 5.x. It reads as the quieter track running beneath the Kit 3 build-up.

    View source ↗