From 6b00f4f30f2899efbf8fe8a25390cd0febf01119 Mon Sep 17 00:00:00 2001 From: "svelte-docs-bot[bot]" <196124396+svelte-docs-bot[bot]@users.noreply.github.com> Date: Thu, 2 Oct 2025 17:50:13 +0000 Subject: [PATCH] sync kit docs --- .../content/docs/kit/10-getting-started/25-project-types.md | 2 +- .../content/docs/kit/25-build-and-deploy/20-adapters.md | 2 +- apps/svelte.dev/content/docs/kit/40-best-practices/06-icons.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/svelte.dev/content/docs/kit/10-getting-started/25-project-types.md b/apps/svelte.dev/content/docs/kit/10-getting-started/25-project-types.md index ec3bdcc0b5..d339671111 100644 --- a/apps/svelte.dev/content/docs/kit/10-getting-started/25-project-types.md +++ b/apps/svelte.dev/content/docs/kit/10-getting-started/25-project-types.md @@ -33,7 +33,7 @@ If you are using an external backend, you can simply skip over and ignore the pa ## Serverless app -SvelteKit apps are simple to run on serverless platforms. [The default zero config adapter](adapter-auto) will automatically run your app on a number of supported platforms or you can use [`adapter-vercel`](adapter-vercel), [`adapter-netlify`](adapter-netlify), or [`adapter-cloudflare`](adapter-cloudflare) to provide platform-specific configuration. And [community adapters](https://sveltesociety.dev/packages?category=sveltekit-adapters) allow you to deploy your application to almost any serverless environment. Some of these adapters such as [`adapter-vercel`](adapter-vercel) and [`adapter-netlify`](adapter-netlify) offer an `edge` option, to support [edge rendering](glossary#Edge) for improved latency. +SvelteKit apps are simple to run on serverless platforms. [The default zero config adapter](adapter-auto) will automatically run your app on a number of supported platforms or you can use [`adapter-vercel`](adapter-vercel), [`adapter-netlify`](adapter-netlify), or [`adapter-cloudflare`](adapter-cloudflare) to provide platform-specific configuration. And [community adapters](/packages#sveltekit-adapters) allow you to deploy your application to almost any serverless environment. Some of these adapters such as [`adapter-vercel`](adapter-vercel) and [`adapter-netlify`](adapter-netlify) offer an `edge` option, to support [edge rendering](glossary#Edge) for improved latency. ## Your own server diff --git a/apps/svelte.dev/content/docs/kit/25-build-and-deploy/20-adapters.md b/apps/svelte.dev/content/docs/kit/25-build-and-deploy/20-adapters.md index a9ef8e6397..b595d10327 100644 --- a/apps/svelte.dev/content/docs/kit/25-build-and-deploy/20-adapters.md +++ b/apps/svelte.dev/content/docs/kit/25-build-and-deploy/20-adapters.md @@ -13,7 +13,7 @@ Official adapters exist for a variety of platforms — these are documented on t - [`@sveltejs/adapter-static`](adapter-static) for static site generation (SSG) - [`@sveltejs/adapter-vercel`](adapter-vercel) for Vercel -Additional [community-provided adapters](https://sveltesociety.dev/packages?category=sveltekit-adapters) exist for other platforms. +Additional [community-provided adapters](/packages#sveltekit-adapters) exist for other platforms. ## Using adapters diff --git a/apps/svelte.dev/content/docs/kit/40-best-practices/06-icons.md b/apps/svelte.dev/content/docs/kit/40-best-practices/06-icons.md index e928642705..e145bc7b5e 100644 --- a/apps/svelte.dev/content/docs/kit/40-best-practices/06-icons.md +++ b/apps/svelte.dev/content/docs/kit/40-best-practices/06-icons.md @@ -9,4 +9,4 @@ A great way to use icons is to define them purely via CSS. Iconify offers suppor ## Svelte -There are many [icon libraries for Svelte](https://www.sveltesociety.dev/packages?category=icons). When choosing an icon library, it is recommended to avoid those that provide a `.svelte` file per icon as these libraries can have thousands of `.svelte` files which really slow down [Vite's dependency optimization](https://vite.dev/guide/dep-pre-bundling.html). This can become especially pathological if the icons are imported both via an umbrella import and subpath import [as described in the `vite-plugin-svelte` FAQ](https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#what-is-going-on-with-vite-and-pre-bundling-dependencies). +There are many [icon libraries for Svelte](/packages#icons). When choosing an icon library, it is recommended to avoid those that provide a `.svelte` file per icon as these libraries can have thousands of `.svelte` files which really slow down [Vite's dependency optimization](https://vite.dev/guide/dep-pre-bundling.html). This can become especially pathological if the icons are imported both via an umbrella import and subpath import [as described in the `vite-plugin-svelte` FAQ](https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#what-is-going-on-with-vite-and-pre-bundling-dependencies).