WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

1.1K

I read more about svelte and sveltekit and I think I have a better handle on it. The one thing the documentation is missing, as far as I am concerned, is a flow of how the processing works.

Off the top of my head, there is a hooks.server.js, a hooks.client.js, a layout.server.js, a layout.js, a page.js and a page.svelte file, and I believe that's everything that is run during a request, but I could be wrong.

There is also a server route that gets called for api requests, initiated by the client. There is a pattern I guess, where layout.server.js, and page.js loads any data from the database or whatever is needed on the server side, and places it in a js object to be automatically serialized and sent to the client.

This all happens at when the page loads. Then, afterwards the client can issue fetch requests and get back serialized objects from json.

That's how I understand it to work. They've recently changed a lot and the examples are not up to date and the documentation is terse. But the framework is pretty good, it seems from my first look at it.

I don't think I'm going to waste my time looking at any more outdated examples, and just try to mess around and get a site up. I'm pretty confident I can make good progress from here on out.

I read more about svelte and sveltekit and I think I have a better handle on it. The one thing the documentation is missing, as far as I am concerned, is a flow of how the processing works. Off the top of my head, there is a hooks.server.js, a hooks.client.js, a layout.server.js, a layout.js, a page.js and a page.svelte file, and I believe that's everything that is run during a request, but I could be wrong. There is also a server route that gets called for api requests, initiated by the client. There is a pattern I guess, where layout.server.js, and page.js loads any data from the database or whatever is needed on the server side, and places it in a js object to be automatically serialized and sent to the client. This all happens at when the page loads. Then, afterwards the client can issue fetch requests and get back serialized objects from json. That's how I understand it to work. They've recently changed a lot and the examples are not up to date and the documentation is terse. But the framework is pretty good, it seems from my first look at it. I don't think I'm going to waste my time looking at any more outdated examples, and just try to mess around and get a site up. I'm pretty confident I can make good progress from here on out.

(post is archived)