Chris Carson

I think imports would be a good option, as would @brewsoftware's idea for a gulp plugin. Here's what I'm currently hacky way of addressing the issue, via gulp. It's slower...

> Weirdly, though, the void returned from src/routes/bad/+page.server.ts is apparently bricking the type for src/routes, up the tree. This was due to `.svelte-kit/types/src/routes/proxy+page.server.ts` not being deleted when I moved `src/routes/+page.server.ts`...

As for the first issue (a `void` return from `+page.server.ts` resulting in `never`) I have gotten so far as giving myself a headache. One thing -- in other though similar...

This might be a good way to handle the problem described in https://github.com/sveltejs/kit/issues/6315

> ActionResult is the type of the JSON response (when you fetch the action, through use:enhance for example). @dummdidumm Ok, thanks. I got the wrong end of the stick somehow....

> I have tested the new update with the same reproduction and the issue still persists. @s3812497 Yep. #6622 fixed something relatively obvious, but there's something else going on here....

@s3812497 Not solving for now, just trying to diagnose. Can you try this, and see whether it works as you intend? In [`src/routes/somewhere/+page.server.ts`](https://github.com/s3812497/sveltekit-enhance-bug/blob/main/src/routes/somewhere/%2Bpage.server.ts) add the options parameter to `cookies.delete` with...

>We talked about issuing a warning in cases like this. One possibility would be to issue a warning here something along the lines of "it seems you want to delete...

> add some kind of warning when omitting the path Yes, in dev. > whether or not we should add more docs on this The cookies API deserves its own...

> It would be great if we can move step 2 to a new function from a load function so it won't block all load functions below it from running....