Hacker News
The SvelteKit 3 Release Candidate is here
division_by_0
|next
[-]
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...
7bit
|previous
[-]
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.
rich_harris
|root
|parent
|next
[-]
For now, we have add-ons for stuff like drizzle and better-auth (https://svelte.dev/docs/cli/overview) which makes it relatively easy to set up these things without committing the framework itself to a particular set of choices. But I totally agree that a lot of the time it's nicer to just not have to think about it. Our current focus is on laying foundations (async Svelte, remote functions, custom renderers etc) but it's very much on our medium term radar.