From 4c884722f86ac8f71d2dc1675151ff3cce9f3ce1 Mon Sep 17 00:00:00 2001 From: Paolo Ricciuti Date: Sat, 3 Oct 2026 12:36:21 +0200 Subject: [PATCH] docs: fix mention of svelte config in best practices (#18917) Closes https://github.com/sveltejs/ai-tools/issues/279 --- documentation/docs/07-misc/01-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/07-misc/01-best-practices.md b/documentation/docs/07-misc/01-best-practices.md index e2cb72828f..d6d0cfcadc 100644 --- a/documentation/docs/07-misc/01-best-practices.md +++ b/documentation/docs/07-misc/01-best-practices.md @@ -167,7 +167,7 @@ Use `createContext` rather than `setContext` and `getContext`, as it provides ty ## Async Svelte -If using version 5.36 or higher, you can use [await expressions](await-expressions) and [hydratable](hydratable) to use promises directly inside components. Note that these require the `experimental.async` option to be enabled in `svelte.config.js` as they are not yet considered fully stable. +If using version 5.36 or higher, you can use [await expressions](await-expressions) and [hydratable](hydratable) to use promises directly inside components. Note that these require the `experimental.async` option to be enabled in the plugin options in `vite.config.js` or in the `svelte.config.js` as they are not yet considered fully stable. ## Avoid legacy features