From 907a213a538533ce4533873d91982efc81cfdf35 Mon Sep 17 00:00:00 2001
From: Simon Holthausen <simon.holthausen@vercel.com>
Date: Wed, 23 Oct 2024 21:01:24 +0200
Subject: [PATCH] docs: note TS caveat about module exports

closes #13554
---
 documentation/docs/01-introduction/03-svelte-files.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/documentation/docs/01-introduction/03-svelte-files.md b/documentation/docs/01-introduction/03-svelte-files.md
index d4c223a7ec..a0c0bf5cc9 100644
--- a/documentation/docs/01-introduction/03-svelte-files.md
+++ b/documentation/docs/01-introduction/03-svelte-files.md
@@ -50,6 +50,8 @@ A `<script>` tag with a `module` attribute runs once when the module first evalu
 
 You can `export` bindings from this block, and they will become exports of the compiled module. You cannot `export default`, since the default export is the component itself.
 
+> [!NOTE] If you are using TypeScript and import such exports from a `module` block into a `.ts` file, make sure to have your editor setup so that TypeScript knows about them. This is the case for our VS Code extension and the IntelliJ plugin, in other cases you might need to setup our [TypeScript editor plugin](https://www.npmjs.com/package/typescript-svelte-plugin).
+
 > [!LEGACY]
 > In Svelte 4, this script tag was created using `<script context="module">`