From f908e2be017219f8af1ca59aebe26dde93fb9bb4 Mon Sep 17 00:00:00 2001
From: Christian Kaisermann <christian@kaisermann.me>
Date: Mon, 6 Jul 2020 21:29:03 -0300
Subject: [PATCH] Add typescript section

---
 docs/migration-guide.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/migration-guide.md b/docs/migration-guide.md
index 1f1a5474..32a2c159 100644
--- a/docs/migration-guide.md
+++ b/docs/migration-guide.md
@@ -4,7 +4,6 @@
 
 <!-- code_chunk_output -->
 
-- [Migration Guide](#migration-guide)
 - [From `v3` to `v4`](#from-v3-to-v4)
   - [Prepending content to `scss`](#prepending-content-to-scss)
   - [Executing some function before preprocessing](#executing-some-function-before-preprocessing)
@@ -88,4 +87,6 @@ sveltePreprocess({
 
 ### Type-checking components
 
-> TODO
+In `v3`, `svelte-preprocess` was able to type-check Svelte components. However, giving the specifics of the structure of a Svelte component and how the `script` and `markup` contents are related, type-checking was sub-optimal.
+
+In `v4`, your TypeScript code will only be transpiled into JavaScript, with no type-checking whatsoever. We're moving the responsibility of type-checking to tools better fit to handle it, such as [`svelte-check`](https://www.npmjs.com/package/svelte-check), for CLI and CI usage, and the [VS Code](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode) extension, for type-checking while developing.