LoginSign Up
← Back to all sparks
S

Svelte

DEVOPS
Velocity5.0

Cybernetically enhanced web apps framework

svelte.dev ↗

SvelteKit 3 reached its Release Candidate with the migration tooling already in the box.

sveltekit-3migration-toolingrelease-candidateagent-toolingmonthly-digest
◆Current state
Svelte 5 core is in steady quality-of-life mode — 5.57 added SvelteMap.getOrInsert and getOrInsertComputed, a has check on createContext, select defaultValue, and exported render-output types. All the directional work sits in SvelteKit 3, which reached a Release Candidate this month after roughly twenty-five @next prereleases. The sv CLI has been reworked around the upgrade: a task-based sveltekit-3 migration bumps dependencies and rewrites $lib to #lib, and newly created projects already default to #lib.
◆Where it's heading
Kit 3 is arriving as a consolidation rather than a rewrite, and the breaking changes stay narrow and mechanical — defineParams moving to @sveltejs/kit/params, cross-page form actions matching native form behavior, adapter Vite plugins split into pre and post groups. The team is running both lines at once: Kit 3 docs live on next.svelte.dev while 2.x still takes patch releases, which is what a low-risk major looks like in practice. Tooling for agent-assisted upgrades is being folded into the same effort, with the mcp add-on replaced by a broader ai-tools add-on covering MCP servers, skills, and sub-agents per client, and sv migrate now emitting a list of leftover changes for a developer or agent to resolve.
◆Prediction
Expect SvelteKit 3.0 stable within the next digest or two, with remaining @next churn confined to adapter and routing internals.

◆Recent moves

  1. 15d 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 ↗
  2. 1mo 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 ↗
  3. 1mo 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 ↗
  4. 2mo 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 ↗
  5. 3mo ago

    Remote functions gain .live() queries and batched requests

    Remote functions stayed the fastest-moving surface, adding .live() real-time queries and query.batch, alongside a breaking requested() change that now requires limit. Still shifting inside the stable 2.x line.

    View source ↗
  6. 4mo ago

    TypeScript 6.0 support and richer remote function transport

    TypeScript 6.0 support and a richer transport for remote functions — quiet groundwork in the months before the Kit 3 preview line opened.

    View source ↗