From b1fc08c6290a1093dddb0a169aae94dde028d78c Mon Sep 17 00:00:00 2001
From: dominikg <dominik.goepel@gmx.de>
Date: Tue, 3 Sep 2024 13:44:47 +0200
Subject: [PATCH 1/3] docs(vitePreprocess): change wording to show that script
 is no longer preprocessed by default

---
 docs/preprocess.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/preprocess.md b/docs/preprocess.md
index a9c1e7de5..543087af9 100644
--- a/docs/preprocess.md
+++ b/docs/preprocess.md
@@ -2,14 +2,14 @@
 
 `vite-plugin-svelte` also exports Vite preprocessors to preprocess Svelte components using Vite's built-in transformers.
 
-Compared to [`svelte-preprocess`](https://github.com/sveltejs/svelte-preprocess), Vite preprocessors share the same CSS configuration from the Vite config so you don't have to configure them twice. [`esbuild`](http://esbuild.github.io) is also used to transform TypeScript by default.
+Compared to [`svelte-preprocess`](https://github.com/sveltejs/svelte-preprocess), Vite preprocessors share the same CSS configuration from the Vite config so you don't have to configure them twice. [`esbuild`](http://esbuild.github.io) can also be used to transform TypeScript.
 
 However, `svelte-preprocess` does provide extra functionalities not available with Vite preprocessors, such as [template tag](https://github.com/sveltejs/svelte-preprocess#template-tag), [external files](https://github.com/sveltejs/svelte-preprocess#external-files), and [global styles](https://github.com/sveltejs/svelte-preprocess#global-style) ([though it's recommended to use import instead](./faq.md#where-should-i-put-my-global-styles)). If those features are required, you can still use `svelte-preprocess`, but make sure to turn off it's script and style preprocessing options.
 
 ## vitePreprocess
 
 - **Type:** `{ script?: boolean, style?: boolean | InlineConfig | ResolvedConfig }`
-- **Default:** `{ script: true, style: true }`
+- **Default:** `{ script: false, style: true }`
 
   A Svelte preprocessor that supports transforming TypeScript, PostCSS, SCSS, Less, Stylus, and SugarSS. These are transformed when the script or style tags have the respective `lang` attribute.
 

From 82aab22040308fe36660630e137854b052c47ace Mon Sep 17 00:00:00 2001
From: dominikg <dominik.goepel@gmx.de>
Date: Tue, 3 Sep 2024 14:36:26 +0200
Subject: [PATCH 2/3] docs(vitePreprocess): more details around new script
 default

---
 docs/preprocess.md | 31 ++++++++++++++++++++++---------
 1 file changed, 22 insertions(+), 9 deletions(-)

diff --git a/docs/preprocess.md b/docs/preprocess.md
index 543087af9..e40bba27f 100644
--- a/docs/preprocess.md
+++ b/docs/preprocess.md
@@ -20,16 +20,29 @@ However, `svelte-preprocess` does provide extra functionalities not available wi
   - SugarSS: `<style lang="sss">`
 
   By default, PostCSS or LightningCSS ([if configured in Vite](https://vitejs.dev/config/shared-options.html#css-transformer)) is applied to all `<style>` tags.
+  If required, you can style transforming off by setting the `style` option to `false`. The `style` option also accepts Vite's `InlineConfig` and `ResolvedConfig` types for advanced usage.
 
-  If required, you can turn script or style transforming off by setting the `script` or `style` option to `false`. The `style` option also accepts Vite's `InlineConfig` and `ResolvedConfig` types for advanced usage.
+  > TypeScript is no longer preprocessed by default as Svelte 5 understands most syntax natively.
+  > If you use TypeScript features that emit code like enum, using , decorators or class declarations with visibility modifiers, you have to enable the script preprocessor manually.
 
-  **Example:**
+### Examples
 
-  ```js
-  // svelte.config.js
-  import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';
+#### default
 
-  export default {
-    preprocess: [vitePreprocess()]
-  };
-  ```
+```js
+// svelte.config.js
+import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';
+export default {
+  preprocess: [vitePreprocess()]
+};
+```
+
+#### enable script preprocessing for advanced TypeScript syntax use
+
+```js
+// svelte.config.js
+import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';
+export default {
+  preprocess: [vitePreprocess({ script: true })]
+};
+```

From d684df8cc6754df55cde65599df4cc9212fbe2e5 Mon Sep 17 00:00:00 2001
From: "Dominik G." <dominik.goepel@gmx.de>
Date: Tue, 3 Sep 2024 15:05:46 +0200
Subject: [PATCH 3/3] Apply suggestions from code review

Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
---
 docs/preprocess.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/preprocess.md b/docs/preprocess.md
index e40bba27f..e4aa014c3 100644
--- a/docs/preprocess.md
+++ b/docs/preprocess.md
@@ -20,10 +20,10 @@ However, `svelte-preprocess` does provide extra functionalities not available wi
   - SugarSS: `<style lang="sss">`
 
   By default, PostCSS or LightningCSS ([if configured in Vite](https://vitejs.dev/config/shared-options.html#css-transformer)) is applied to all `<style>` tags.
-  If required, you can style transforming off by setting the `style` option to `false`. The `style` option also accepts Vite's `InlineConfig` and `ResolvedConfig` types for advanced usage.
+  If required, you can turn transforming off by setting the `style` option to `false`. The `style` option also accepts Vite's `InlineConfig` and `ResolvedConfig` types for advanced usage.
 
-  > TypeScript is no longer preprocessed by default as Svelte 5 understands most syntax natively.
-  > If you use TypeScript features that emit code like enum, using , decorators or class declarations with visibility modifiers, you have to enable the script preprocessor manually.
+TypeScript is no longer preprocessed by default as Svelte 5 understands most syntax natively.
+If you use TypeScript features that emit code (like `enum`, `using`, `accessors`, decorators or class declarations with visibility modifiers), you have to enable the script preprocessor by setting the `script` option to `true`.
 
 ### Examples