Update Svelte docs

[didier]

Just some small tweaks that removes reference to "svelte 5 preview" and the old npm create CLI in favor of the current npx sv create pattern, as well as a wrong reference of src/routes/page.tsx.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[Nicolapps]

I think that this change shouldn’t be applied because convex and convex-svelte are used at runtime.

Suggested change

	cd my-app && npm install -D convex convex-svelte
	cd my-app && npm install convex convex-svelte

[didier]

In Svelte everything gets compiled in, it's normal for everything to be a dev dependency unless you specifically want something to be externalized

I have multiple large repos (not Convex) with only devDependencies.

It's worth testing if this correctly compiles for prod too, but I'm pretty sure it will

[nipunn1313]

@thomasballinger ?

[thomasballinger]

We can try this, but is there any downside to putting it in deps instead of dev deps @didier? This distinction is still made in some svelte apps, in which case these are deps, not dev deps (the convex cli is a dev dep, but it's the same package as convex/server (compiled into convex functions) and convex/browser (compiled into svelte client and (I hope? with every adapter?) bundled into server bundles). If a developer publishes their package to reuse functionality in lib/ then they'll probably need to move convex back to deps.

I thought there were issues where the server-side code is not bundled in some situations, maybe that's all been resolved as server endpoints are always bundled?

I'd rather not just so we can skip the step where we explain that if you reuse code from this package you need to move it.