LoginSign Up
← Back to all sparks
S

Svelte

DEVOPS
Velocity0.0

Cybernetically enhanced web apps framework

svelte.dev ↗

SvelteKit 3 shipped as a tidy-up; remote functions, its top priority, did not make it.

sveltekit-3remote-functionsasync-sveltemigration-toolingsv-cli
◆Current state
SvelteKit 3.0 is out, with sv 1.0 released the same day and the community add-on API now official. The announcement describes the same framework with more polish: configuration in vite.config.ts, $lib replaced by #lib, reworked environment variables, simpler service workers and better error handling. sv migrate handles most of the upgrade and generates a TODO list for the rest. Svelte core was quiet, with 5.57.1 limited to bug fixes and parser performance.
◆Where it's heading
The major version consolidates rather than reinvents, but the last prereleases still carried real breakage for platform teams: Cloudflare's platform object is gone in favor of an emulated cloudflare:workers module, and adapter-node now serves only static assets present at build time. Remote functions are the open item. The team calls them its top priority, and they depend on Async Svelte, which still needs an experimental flag.
◆Prediction
The next directional move is Async Svelte and remote functions leaving their experimental state. Svelte Summit in Ljubljana on November 19-20 is the obvious stage, though the entries do not promise an announcement there.

◆Recent moves

  1. 1mo ago

    sv 1.0, Render deploys and the last SvelteKit 3 breaking changes

    The digest records the final prerelease changes: adapter API updates, zero-config Render deploys through adapter-auto, a Cloudflare move to cloudflare:workers and stricter static serving in adapter-node. It shows where the 3.0 upgrade costs fall, which is on adapter and platform code rather than app code.

    View source ↗
  2. 1mo ago

    SvelteKit 3 is here

    The release the RC and @next line were building to, and it arrives as promised: a consolidation with narrow breaking changes and an automated migration path. Remote functions were not ready, so 3.0 closes the cleanup arc rather than opening a new one.

    View source ↗
  3. 2mo ago

    SvelteKit 3 hits RC; sv CLI swaps mcp for an ai-tools add-on

    The September digest puts SvelteKit 3 at Release Candidate and reworks sv migrate into a task-based sveltekit-3 path that bumps dependencies and rewrites $lib to #lib. Svelte 5.57 itself is quality-of-life work. The mcp add-on is replaced by a broader ai-tools add-on that configures MCP servers, skills, and sub-agents per client.

    View source ↗
  4. 2mo ago

    The SvelteKit 3 Release Candidate is here

    The Release Candidate closes the preview line that opened in August, taking Kit 3 from thirteen @next builds to a named candidate. It confirms the arc is a consolidation of work already running in the 2.x line rather than a rewrite.

    View source ↗
  5. 3mo ago

    SvelteKit 3 opens its preview line with 13 @next releases

    ⚡ SPARK

    The month SvelteKit 3 became testable: thirteen @next releases through July put $app/manifest and $app/service-worker, tracing promoted out of the experimental namespace, and shallow routing folded into goto in front of teams. This is the origin of the Kit 3 arc that the RC and the migration tooling are now executing on.

    View source ↗
  6. 4mo ago

    SvelteKit config moves into vite.config.js

    Config moving into vite.config.js made svelte.config.js optional — an early piece of the flattening that Kit 3 later formalized in its config structure.

    View source ↗