I really like how with React (and a few others) you can make a quick abstraction in the same file for a repeated chunk of the render. Sometimes something warrants pulling out into a function for reusability but it doesn’t quite pass the bar to justify its own file as a component - I know there’s some template stuff coming in Svelte 5, so hopefully that scratches the itch.
this post was submitted on 22 Nov 2023
1 points (100.0% liked)
Svelte + SvelteKit
539 readers
1 users here now
Svelte is a JavaScript framework for building user interfaces (UIs) that compiles your code into efficient JavaScript during the build process, resulting in better performance and smaller bundle sizes. Svelte focuses on reactive programming, where UI components update themselves when data changes, eliminating the need for a virtual DOM. Svelte Kit is an extension of Svelte that adds features like routing and server-side rendering, simplifying the creation of full-stack web applications. It provides file-based routing and supports server-side rendering, enabling faster initial page loads and improved search engine optimization. Svelte Kit combines client-side Svelte components with server-side rendering and serverless functions for a seamless development experience.
founded 1 year ago
MODERATORS
Totally agree, I can definitely say I’ve found myself wishing for that more as I continue to use Svelte. I didn’t see it as necessary at first, but situations that could benefit from that have come up enough now that I’ve used it for a while
This seems to now be possible thanks to Svelte 5 Snippets
Oh wow, thanks for sharing. Hadn’t heard of that yet, it definitely makes it possible but that syntax will take some getting used to
Kinda wish it had DI, coming from Angular and C# it's so helpful to have stateful services, I know one answer is to just use a global static, but that causes huge issues on the server side and it's really easy to make mistakes there. It feels like contexts are the answer, but then you can't use those services in load functions.
I'm curious where do you store the current user data. In a static store? Return it from a load function and access it via the page store? Somewhere else?
Well, I usually fetch and return user data from a top-level +layout.js or +layout.server.js. Then my user data is always available in every layout or page through the data prop (and types are all handle automatically for this too).
I then invalidate and re-fetch that data using invalidate(), invalidateAll(), and depends() if the user data becomes stale.
Any state/data from the user that needs to stay server-side (like tokens) I keep in event.locals which is available in all .server.js files