SvelteKit reaches its 1.0 release

The Svelte team released SvelteKit 1.0 on 14 December, bringing its application framework to a stable milestone after two years of development. The team now recommends it for building Svelte applications.

Svelte supplies interface components; SvelteKit handles the surrounding application. The release brings routing, server rendering and deployment into a common framework, rather than leaving developers to assemble that infrastructure themselves.

Rendering can vary by page

The 1.0 documentation describes a default of rendering HTML on the server, then hydrating it in the browser. Pages can instead be prerendered during the build. Server rendering and client rendering can be disabled separately, with options applied through pages or layouts.

Routing, data and forms

In Vercel’s launch-day walkthrough, the application’s route structure follows its directories. Shared layouts carry elements such as headers between pages. A load function supplies page data, while a server-only file keeps that loading logic on the server. These conventions give teams a common place for responsibilities that otherwise tend to spread across an application.

Form actions accept POST requests in server-side page code. A standard HTML form can invoke them without client-side JavaScript, while progressive enhancement adds interaction when JavaScript is available. The documentation recommends actions for sending data to the server because they can support both modes.

Upgrading from the preview

Existing users are advised to move through the final prerelease, 1.0.0-next.588, before installing 1.0. The stable version removes migration warnings and errors that helped users navigate earlier breaking changes.