| ▲ | The SvelteKit 3 Release Candidate is here(svelte.dev) | ||||||||||||||||||||||
| 24 points by pier25 2 days ago | 5 comments | |||||||||||||||||||||||
| ▲ | division_by_0 a day ago | parent | next [-] | ||||||||||||||||||||||
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... | |||||||||||||||||||||||
| ▲ | 7bit 2 days ago | parent | prev [-] | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| |||||||||||||||||||||||