Hofer Ivan

Adding my two cents here: Handling authorization is currently easy to mess up. 1. The main issue was already described above:\ If you don't explicitly run all checks on each...

> Would whatever is exported from `routes/kittens/[id]/dashboard/+auth.server.ts` run before **all** the descendant loads? For example, would it run before the load in `routes/kittens/[id]/dashboard/revenue/+page.server.ts`? Or is is just run before the...

> I'm currently not aware of any usecase where something would need to run in a similar way for the full tree as authorization requires it Found another use-case where...

@coryvirok I agree, in `SvelteKit`s current state, auth handling is best handled in `hooks.server.js`, if you really want to make sure to not accidentially introduce security vulnerabilities. For static routes...

I have spent some hours to create a repository that should demonstrate the pain-points of using authorization in a current `SvelteKit` project: https://github.com/ivanhofer/sveltekit-auth It also shows how the `+auth.server.ts` proposal...

@whalemare I saw this PR was not updated for a while. Do you plan to continue working on this PR?

No it's fine. We can keep it open if you plan to continue working on it.

Yes, this is the issue. The error gets logged here: https://github.com/ivanhofer/typesafe-i18n/blob/main/packages/cli/src/setup/runtimes/node.mts#L44-L62 We would need to find a way to detect if the command runs inside a workspace. DO you know...

Can you please share a repo where I can reproduce this?

You can use the same code as you would write a server-application. The only thing that really changes is that you can't use the `/` route to detect the user's...