Chris Carson

It's an hmr issue. So it would only evidence itself when you were running the app locally. It wouldn't show up running the app on StackBlitz.

@dankochetov Quick related question based on your response above. Can I throw my own error rather than calling `tx.rollback()`, i.e. something like this... ```ts await db.transaction(async (tx) => { await...

Maybe related or fixable at the same time. Fresh install of SvelteKit with `data-sveltekit-preload-data="hover"` in the body tag. If I have a link to a `+server.ts` GET endpoint I repeatedly...

> we landed on defaulting to data I'm not set against it. There's a benefit for certain types of pages. But it seems like it could put more load on...

@Rich-Harris My gut is that this is a "more documentation" issue. `event.alwaysRun()` could just as well be omitted as `await parent()` (or however it is now recommended to ensure the...

Ack, I see I wrote this: > Granted, to footgun the omission is in one +layout.server.js rather than in each leaf. Might make sense. Ungarbled: For the vector to be...

@TranscendentalRide Adding an `+auth.server.js` filename would light a dumpster fire 🔥. (See the discussions in the repo.) But I see where you're going. Right now the `+layout.server` load tree is...

@ivanhofer Question. Let's say I have a whole bunch of routes for `kittens/[id]/dashboard`, all of which share the same authorization logic... ```bash . └── routes └── kittens └── [id] └──...

I'm of two minds about this. If SvelteKit keeps the notion of `layout.server.ts` it should definitely provide a way to guard routes hierarchically (i.e. what @ivanhofer is talking about, where...

Some thoughts. Usual caveats about IMO, etc. The original issue was just about how `+layout.server.js` is presented. It's a browser cache, not middleware. The issue pointed out that it might...