5 comments

[ 1.8 ms ] story [ 12.3 ms ] thread
I love Svelte and SvelteKit. But I keep going back to the batteries-included Django simply for the ORM, the admin backend and authentication packages. Nothing in the JS ecosystem comes close to it in terms of simplicity and integration-level and using third party modules always feels hacky and they pull in a thousand other dependencies.

I wish SvelteKit would become batteries-included, but that's not the direction they have in mind -- which is totally fair. It makes me sad nonetheless.

Looks good. Will def migrate my current project before publishing it.

A detail I find interesting:

> version.pollInterval now defaults to one hour, meaning SvelteKit will periodically check for new deployments and set updated.current to true accordingly. Previously, no polling occurred by default. [0]

I always use this in my projects combined with updated.check() when the doc becomes visible, but some people will probably not read this and see unexpected requests in prod.

[0] https://next.svelte.dev/docs/kit/migrating-to-sveltekit-3#Co...

sveltekit - the problem is they can't settle and not change the api frequently.

every release is a breaking change.

What a ridiculous comment. This is the first major release of SvelteKit in three years; the last major release of Svelte was two years ago.