# What's the deal with SvelteKit?

DevFeed: [What's the deal with SvelteKit?](<https://devfeed.tech/articles/what-s-the-deal-with-sveltekit-3128.md>)

Original publisher: [Read original article](<https://svelte.dev/blog/whats-the-deal-with-sveltekit>)

Author: Rich Harris

Published: 2020-11-05T00:00:00Z

Content type: article

Language: en

Sources: [Svelte blog](<https://devfeed.tech/sources/svelte-blog.md>)

Topics: [Svelte](<https://devfeed.tech/topics/svelte.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Development](<https://devfeed.tech/topics/development.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Template](<https://devfeed.tech/topics/template.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>), [Webpack](<https://devfeed.tech/topics/webpack.md>)

Tags: [code-splitting](<https://devfeed.tech/tags/code-splitting.md>), [development](<https://devfeed.tech/tags/development.md>), [framework](<https://devfeed.tech/tags/framework.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [project](<https://devfeed.tech/tags/project.md>), [routing](<https://devfeed.tech/tags/routing.md>), [server-side-rendering](<https://devfeed.tech/tags/server-side-rendering.md>), [ssr](<https://devfeed.tech/tags/ssr.md>), [support](<https://devfeed.tech/tags/support.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [webpack](<https://devfeed.tech/tags/webpack.md>)

## AI overview

This article explains that Sapper will not reach version 1.0 because its successor, SvelteKit, is effectively a rewrite and rebrand. It describes Sapper as a Svelte-based app framework that supports server-side rendering, code-splitting, filesystem-based routing, and a productive project structure, then outlines migration motivations including simpler onboarding, lower maintenance and support burden, and reconsideration of module-bundling assumptions.

## Source excerpt

If you didn't attend Svelte Summit, you can catch up on the Svelte Society YouTube page If you attended Svelte Summit last month you may have seen my talk, Futuristic Web Development, in which I finally tackled one of the most frequently asked questions about Svelte: when will Sapper reach version 1.0? The answer: never. This was slightly tongue-in-cheek -- as the talk explains, it's really more of a rewrite of Sapper coupled with a rebrand -- but it raised a lot of new questions from the community, and it's time we offered a bit more clarity on what you can expect from Sapper's successor, SvelteKit. 'Futuristic Web Development' from Svelte Summit What's Sapper? Sapper is an app framework (or 'metaframework') built on top of Svelte (which is a component framework). Its job is to make it easy to build Svelte apps with all the modern best practices like server-side rendering (SSR) and code-splitting, and to provide a project structure that makes development productive and fun. It uses filesystem-based routing (as popularised by Next and adopted by many other frameworks, albeit with some enhancements) -- your project's file structure mirrors the structure of the app itself. While the Svelte homepage and documentation encourages you to degit the sveltejs/template repo to start building an app, Sapper has long been our recommended way to build apps; this very blog post is (at the time of writing!) rendered with Sapper. Why are we migrating to something new? Firstly, the distinction between sveltejs/template and sveltejs/sapper-template is confusing, particularly to newcomers to Svelte. Having a single recommended way to start building apps with Svelte will bring enormous benefits: we simplify onboarding, reduce the maintenance and support burden, and can potentially begin to explore the new possibilities that are unlocked by having a predictable project structure. (This last part is deliberately vague because it will take time to fully understand what those possibilities ar