Skip to content

SYSTEM Cited by 1 source

SvelteKit

SvelteKit (svelte.dev/docs/kit) is the Svelte-team's application framework for Svelte, built on top of Vite with file-based routing, server-side rendering, and server endpoints. Part of the Vite-based framework family alongside Astro, Nuxt, Remix.

Stub

This page covers only what currently-ingested sources name about SvelteKit. Broader SvelteKit internals (form actions, load functions, adapters, SSR/CSR/SSG modes) are out of scope until a source discusses them.

Relevance to the wiki (2026-04-21)

Worked-example framework in Vercel's 2026-04-21 WDK post — the post walks the SvelteKit integration in detail as the case study for the two-phase framework integration pattern:

  • Build-time: SvelteKit expects handlers named +server.js under src/routes/*; WDK's SvelteKit builder outputs two esbuild bundles (step-mode + workflow-mode) into src/routes/.well-known/workflow/v1.
  • Runtime: SvelteKit's file-based routing auto-discovers the +server.js files as HTTP endpoints — "as long as the file is named +server.js. No manual wiring needed."

Relevant framework properties (named by ingested sources)

  • File-based routing — canonical file- based-routing framework; routes are files under src/routes/.
  • +server.js convention — SvelteKit-specific server endpoint filename. WDK outputs generated handlers under this name to leverage auto-discovery.
  • Custom request object — SvelteKit passes a custom request object to route handlers, not the standard Web Request API. This is the friction that motivates WDK's injected request-object converterconvertSvelteKitRequest bridges the gap.
  • Vite-based — builds via Vite; WDK hooks into Vite's hotUpdate lifecycle for HMR via patterns/vite-hotupdate-directive-triggered-rebuild.

Adoption datum

Per Vercel's 2026-04-21 post verbatim: "The SvelteKit integration alone brought workflows to thousands of developers already building in that ecosystem." Marketing-register claim.

Seen in

Last updated · 476 distilled / 1,218 read