From 12b6207db0a9edbde5a80a9c5e0d5dfb2fc3cfbb Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Tue, 3 Nov 2020 23:30:20 -0500 Subject: [PATCH] tweak migration section --- .../blog/2020-11-02-whats-the-deal-with-sveltekit.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md b/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md index 033ba74a06..acaa38beb1 100644 --- a/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md +++ b/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md @@ -76,7 +76,11 @@ Don't worry, we won't launch without full TypeScript support. ## How can I migrate my existing Sapper apps? -Detailed migration guides will accompany the 1.0 launch. For the most part, it should be relatively straightforward to migrate a Sapper codebase — there are some unavoidable changes (being able to run on serverless platforms means no more custom `server.js`, for example, and no more `req` and `res` objects in your handlers), and a few design flaws that we're taking the opportunity to fix, but on the whole a SvelteKit app will feel very familiar to Sapper users. +For the most part, it should be relatively straightforward to migrate a Sapper codebase. + +There are some unavoidable changes (being able to run on serverless platforms means we need to replace custom `server.js` files and `(req, res) => {...}` functions with more portable equivalents), and we're taking the opportunity to fix a few design flaws, but on the whole a SvelteKit app will feel very familiar to Sapper users. + +Detailed migration guides will accompany the 1.0 launch. ## How can I contribute?