You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[With Svelte VS Code](#with-svelte-vs-codehttpsmarketplacevisualstudiocomitemsitemnamejamesbirtlessvelte-vscode)
17
+
-[With Sapper](#with-sapper)
18
+
-[With Svelte VS Code](#with-svelte-vs-code)
19
19
-[Preprocessing modes](#preprocessing-modes)
20
20
-[Auto Preprocessing](#auto-preprocessing)
21
21
-[Standalone processors](#standalone-processors)
@@ -180,9 +180,9 @@ export default {
180
180
...
181
181
```
182
182
183
-
### With [Sapper](https://sapper.svelte.dev/)
183
+
### With Sapper
184
184
185
-
Sapper has two build configurations, one for the client bundle and one for the server. To use `svelte-preprocess` with Sapper, you need to define it on both configurations.
185
+
[Sapper](https://sapper.svelte.dev/) has two build configurations, one for the client bundle and one for the server. To use `svelte-preprocess` with Sapper, you need to define it on both configurations.
186
186
187
187
```js
188
188
// ...
@@ -212,9 +212,9 @@ export default {
212
212
};
213
213
```
214
214
215
-
### With [Svelte VS Code](https://marketplace.visualstudio.com/items?itemName=JamesBirtles.svelte-vscode)
215
+
### With Svelte VS Code
216
216
217
-
`svelte-vscode` needs to know how its (svelte) language server should preprocess your files. This can be achieved by creating a `svelte.config.js` file at the root of your project which exports a svelte options object (similar to `svelte-loader` and `rollup-plugin-svelte`).
217
+
[svelte-vscode](https://marketplace.visualstudio.com/items?itemName=JamesBirtles.svelte-vscode) needs to know how its (svelte) language server should preprocess your files. This can be achieved by creating a `svelte.config.js` file at the root of your project which exports a svelte options object (similar to `svelte-loader` and `rollup-plugin-svelte`).
0 commit comments