feat(create-vite): update to svelte 5

[sapphi-red]

Description

I simply ran npx sv@latest migrate svelte-5 and changed the svelte version to ^5.0.3 from ^5.0.0.

• svelte
• svelte-ts

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[bluwy]

The import './index.css' import order has implication if nested components also import global css, since the ordering happens on which side-effect import happens first. But sorting it to the bottom shouldn't cause too much issue I think, it was already happening for some templates.

[bluwy]

Actually, it seems like it's affecting the React template. For example between index.css and App.css. I think I'd expect index.css to have the higher priority (placed first) in the bundled CSS output. So maybe we should be putting these global CSS top before any imports for consistency 🤔

[sapphi-red]

Ah, that's true.

[benmccann]

I think there's someplace that the CLI invokes npm create svelte if you want to create a SvelteKit app? Can we have it invoke npx sv create instead? There's a pretty good chance that npm create svelte goes away shortly. (I have a PR to do that out for discussion: sveltejs/kit#12850)

[benmccann]

I pushed that change. This looks good to me now