kit

This reminds me of the recent SvelteKit Remote Functions GH discussion: > Even in systems that prevent server functions from being declared in client code (such as "use server" in React Server Components), experienced developers can be caught out. We prefer a design that emphasises the public nature of remote functions rather than the fact that they run on the server, and avoids any confusion around lexical scope. [0] [0] https://github.com/sveltejs/kit/discussions/13897

The number 3, 4, and 5 contributors to SvelteKit in the past year work at Vercel: https://github.com/sveltejs/kit/graphs/contributors?from=8%2... Rich and Simon are incredibly important, but they're in it for Svelte and the community more so than a paycheck from Vercel. Tee has been doing most of the maintenance on SvelteKit currently funded by community donations. And this isn't counting other infrastructure like vite-plugin-svelte or the Svelte CLI which are entirely maintained by volunteers. I don't think Vercel funds a majority of the work on Svelte even if it might be close to it.

This is great! Locality of Behaviour is of special interest to me. How is your experience with currentScript.parentElement? Last month I did a quick research and my impression is that it wasn't reliable in some probably niche case but I can't remember when. But I didn't investigate much and I'm glad you made it work! If I load 3 consecutive scripts currentScript.parentElement should still work in all browsers right? As long as it is not async or module, which is fine with me. SvelteKit had this conversation and they ended up implementing random ids for elements to set their targets: https://github.com/sveltejs/kit/issues/2221

Thanks. also this https://github.com/sveltejs/kit/discussions/4339#discussionc...

Of course! I was very used to SPA, and the convenience of moving a rune/store to an external file meant it could be accessed anywhere (as the post said). With SSR however, if you’re not careful, you can easily leak data: https://github.com/sveltejs/kit/discussions/4339.

SvelteKit is a great way to build a SPA. I think just adding those two lines of config to your project once shouldn't be an issue. If there are any difficulties you'd like to share we'll try to fix them as part of SvelteKit 3. (e.g. this issue which I added to the 3.0 milestone: https://github.com/sveltejs/kit/issues/12580)

Sequel: https://github.com/sveltejs/kit/issues/11924

Glad that inlang could contribute i18n routing capabilities for SvelteKit 2.0! https://inlang.com/c/svelte and https://github.com/sveltejs/kit/pull/10755

I just started a project and chose this stack: - SSR SvelteKit with Hydration (https://github.com/sveltejs/kit) - PostgreSQL database server - Postgres.js - PostgreSQL client for Node.js (https://github.com/porsager/postgres) - Migration powered by graphile-migrate (https://github.com/graphile/migrate) - PostgreSQL Row-Level Security (https://www.postgresql.org/docs/16/ddl-rowsecurity.html) - svelte-headlessui (https://github.com/rgossiaux/svelte-headlessui) - sveltekit-i18n (https://github.com/sveltekit-i18n/lib) - TailwindCSS (https://tailwindcss.com/) - Superforms (https://superforms.rocks/) - sveltekit-flash-message + svelte-french-toast (https://github.com/ciscoheat/sveltekit-flash-message + https://github.com/kbrgl/svelte-french-toast) Tooling : - asdf (https://asdf-vm.com/) - Docker and Docker Compose - NodeJS - pnpm - Jest for uni