Jonathan Gamble

@tcc-sejohnson - Didn't realize that, good to know. However, this doesn't solve the problem of running them separately instead of consecutively. @david-plugge - Not sure what you mean. I can...

@david-plugge - So it seems I can skip the load function on `+page.server.ts` if I use this code... ```ts export const load = (async ({ params, request }) => {...

Ok, so you definitely got me where I needed to be after changing your code: **+page.server.ts** ```ts export const load = (async ({ isDataRequest }) => { if (isDataRequest) {...

Ah, yes very true. I don't think that helps me in this particular situation, as I need to not get the slug on route change sometimes, but good to know,...

> SvelteKit is smart enough to treat it as a regular function call, so the only overhead is converting to and from a Response Very very interesting and good to...

Yup, this is definitely a problem. If the `catch` on the frontend doesn't work, this is useless. I don't think the docs need to get updated as much as this...

@gtm-nayan - I think if this can't be done for now, you guys need to update the docs explaining this clearly perhaps with an example workaround. If the `await catch`...

The `window` fetch though is different than SvelteKit's `fetch`. I would think the simple answer would be to add the ability to just use `hooks.ts` like `page.ts`: - hooks.server.ts -...

We need to reopen this again. Now that `Edge Functions` are popular, we need `Firebase Admin Lite` SDK to be allowed to handle session variables and fetch calls with the...

`@napi-rs/image` won't work on Edge Functions fwi. J