docs: clarify what you can build with SvelteKit

[benmccann]

I've seen a really depressing number of people saying you can't build a SPA with SvelteKit. Some portion of that may be due to sveltejs/kit#12580, which I'm working on, but I also think some of it is just ignorance or confusion. I'm hoping this change will help on the education side

[changeset-bot]

⚠️ No Changeset found

Latest commit: a1eb1e4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-svelte-15461-svelte.vercel.app/

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@15461

[benmccann]

The deploy is failing, but is sure looks like its caching an old version and I'm not sure how to address that as I've tried redeploying already. I would say we should just merge this if we're happy with the text and if it's still an issue in the sveltejs/svelte.dev PR then I can look at it some more then

[dummdidumm]

what about making it a callout note? The current change makes it sound like vanilla Vite is only valid if you're doing SPA.

Suggested change

	If you're building a [single page app (SPA)](../kit/glossary#SPA), you can [use SvelteKit](../kit/single-page-apps), or you can use Svelte directly with Vite. To create a vanilla Vite project, run `npm create vite@latest` and selecting the `svelte` option. With this, `npm run build` will generate HTML, JS and CSS files inside the `dist` directory using [vite-plugin-svelte](https://github.com/sveltejs/vite-plugin-svelte). In most cases, you will probably need to [choose a routing library](faq#Is-there-a-router) as well.
	You can also use Svelte directly with Vite by running `npm create vite@latest` and selecting the `svelte` option. With this, `npm run build` will generate HTML, JS and CSS files inside the `dist` directory using [vite-plugin-svelte](https://github.com/sveltejs/vite-plugin-svelte). In most cases, you will probably need to [choose a routing library](faq#Is-there-a-router) as well.
	>[!NOTE] If you only choose vanilla Vite because you're building a [single page app (SPA)](../kit/glossary#SPA), you can also [use SvelteKit](../kit/single-page-apps)

[benmccann]

The current change makes it sound like vanilla Vite is only valid if you're doing SPA.

I think that's basically all vanilla Vite is used for. It's too complex to do SSR without a framework. Was there something else you had in mind that people might build?