// the find
sveltejs/kit
web development, streamlined
SvelteKit is the official full-stack framework for Svelte, covering routing, server load functions, form actions, and deployment adapters for Node, Vercel, Netlify, Cloudflare, static hosting, and others. It is for developers building a Svelte app beyond a single page who want the framework the Svelte team maintains rather than a community wrapper.
- Deployment targets are separate adapter packages (adapter-node, adapter-static, adapter-vercel, adapter-cloudflare and more), each with its own changelog, so you only pull in the output format you need.
- Several adapters ship with their own test/apps directory and Playwright config, so a regression in one platform's build output is caught in CI rather than in a user's deploy.
- Changesets drive versioning, and each package keeps its own CHANGELOG.md, which makes it possible to see what changed in the exact package you upgrade.
- The docs live in the same repo under documentation/docs, including per-module reference pages for $app and $lib, so doc changes can land in the same PR as the code they describe.
- The root README is little more than a link to the docs site, so setup and architecture questions push you out of the repo. The directory tree does not explain the core runtime without digging into packages/kit.
- Many build problems originate in Vite, and the project sends those reports to the Vite tracker. A user with a broken build may have to work out which of the two projects owns the bug.
- Nine packages released from one monorepo means a @sveltejs/kit version does not guarantee matching adapter versions. Community adapters, listed on an external site, get less attention than the official ones.
- Adapter behaviour still differs across platforms in ways the shared abstraction does not hide, such as edge runtimes, filesystem access, and prerender limits. Switching hosts means checking each adapter's own README and limitations.