← All posts

Svelte, September 2026: SvelteKit 3 RC, SvelteMap, and sv migration

Svelte 5.57 adds SvelteMap getOrInsert; SvelteKit 3 Release Candidate; ai-tools replaces mcp; sveltekit-3 task in sv migrate.

Tags
Newsfrontendsveltesveltekit
Svelte, September 2026: SvelteKit 3 RC, SvelteMap, and sv migration
Contents

In brief

September 2026 digest: Svelte 5.57 with SvelteMap helpers and form tweaks; SvelteKit 3 hits Release Candidate; sv CLI gets ai-tools (replacing mcp) and a sveltekit-3 migration task in sv@next.

What happened

Svelte 5.57:

  • SvelteMap.getOrInsert and getOrInsertComputed for read-or-init patterns;
  • createContext returns a third has function — check context without triggering get errors;
  • <select> supports defaultValue on form reset;
  • svelte/server exports RenderOutput, Csp, Sha256Source types.

SvelteKit 3 RC (@next):

  • cross-page form actions navigate to the action page on success/failure (breaking);
  • adapter Vite plugins split into pre/post groups;
  • colocated test/spec/stories files no longer become routes;
  • +server.js can export a QUERY HTTP handler;
  • defineParams moved to @sveltejs/kit/params.

CLI and tooling:

  • ai-tools add-on sets up Svelte plugin for Claude Code / opencode or individual MCP, skills, sub-agents;
  • sv migrate reworked: task list, sveltekit-3 (dependency bump, $lib → #lib), $app/state task, manual follow-ups list;
  • new projects use #lib (Node subpath imports);
  • community add-ons no longer require scoped package names.

Stable SvelteKit 2.x got three patch releases (2.70.1–2.70.3).

Why it matters

SvelteKit 3 is a real major: imports (#lib), form actions, route params, and config shape all shift. RC means migration planning starts now, not “after stable.”

The sveltekit-3 task in sv migrate partially automates a major upgrade — unusual for frontend frameworks. ai-tools signals intentional agent-dev ergonomics in the Svelte stack.

In practice

  1. Bump to Svelte 5.57 — getOrInsert helps anywhere you use SvelteMap.
  2. For Kit 3: docs on next.svelte.dev, changelog on version-3 branch.
  3. Run sv migrate with sveltekit-3 on a repo copy — review manual items.
  4. Replace mcp add-on with ai-tools if you used the old Svelte MCP server.
  5. Stay on 2.70.x patches until ready for Kit 3 breaking changes.

Takeaway

September 2026 is when SvelteKit 3 stopped being hypothetical: RC, CLI migration task, and ai-tools for agents. Teams on Svelte should start a migration spike, not wait for the next digest.