4 ms·
This blog post gives a bit more information on that: https://svelte.dev/blog/whats-the-deal-with-sveltekit https://svelte.dev/blog/whats-the-deal-with-sveltekit
by rich_harris 6y ago
This blog post gives a bit more information on that: https://svelte.dev/blog/whats-the-deal-with-sveltekit https://svelte.dev/blog/whats-the-deal-with-sveltekit, though the section on Snowpack is out of date. Basically, SvelteKit is serverless-first (whereas Sapper made you choose between a Node server and prerendered HTML), and because it's powered by Vite has a much nicer developer experience.
It also fixes a few of the rough design edges in Sapper. This migration guide gives you an idea of the scope of the changes: https://kit.svelte.dev/migrating https://kit.svelte.dev/migrating
- pier25 6y agoHey Rich, is partial hydration on your roadmap for SvelteKit?
- rich_harris 6y agoThat's a Svelte issue rather than a SvelteKit issue. It's on our _radar_, though I don't know if I'd say it's on our _roadmap_ just yet
- swyx 6y agoi would also like this. i recall Rich musing on some of the "hydrating unnecessary content" problems in this post https://dev.to/richharris/in-defense-of-the-modern-web-2nia https://dev.to/richharris/in-defense-of-the-modern-web-2nia so i imagine its on his mind. Elder.js solved it in a way, i'd love to see Rich's spin on it.
- m8s 6y agoOh, awesome, thanks for responding. Excited to give SvelteKit a try!