sveltekit-firebase-ssr VS auth-helpers

This repo has a good working example of how they handle and manage with authentication.

This repo will have exactly the examples you'll need to structure your svelte app around Firebase. I use this as a reference a ton and it's helped me out in terms of using it and SSR. :)

Maybe have a look at this library and see what you've done differently. https://github.com/ManuelDeLeon/sveltekit-firebase-ssr

Good example can be found here

What does API helper do? The hook is called every single time anything pings/visits the website. If you want a good example of the API and how specific things work, you can take a look at svelte-firebase-ssr

I couldn't find a straightforward example of SSR'ing user data from Firebase so I created this starter project: https://github.com/ManuelDeLeon/sveltekit-firebase-ssr

I have encountered a similar issue, but I haven't fully found a solution yet. Currently, I'm using the getSession function throughout my server components. Yesterday, I tried running a middleware to refresh the user's session, based on this example: https://github.com/supabase/auth-helpers/blob/main/examples/nextjs/middleware.tsx. This caught my attention because the comment mentioned that the middleware is necessary for any Server Component route using createServerComponentClient. Right now, I'm testing this approach, and so far, I haven't been logged out since yesterday. Do you have that in your application? The main difference between getSession and getUser in supabase is that getSession reads the cookies and is very fast (around 1-2 ms), while getUser makes a call to the supabase API with the access token to retrieve the user and I would assume they also verify the JWT on their end.

F.ex. Have a look how supabase-auth-helper-sveltekit works. This is the "SvelteKit way" to approach authentication. It also works perfectly with invalidate to reload or invalidate data that is connected to the current user session. As pointed out already, there is no reason you should not be able to access your JWT.

We have updated the Next.js Auth Helpers package to make it available across the client and server of the App Router. They also now implement server-side auth by default with PKCE - meaning the entire auth flow is now possible server-side.

Example

seems like known issue https://github.com/supabase/auth-helpers/issues/497

auth helper for sveltekit: https://github.com/supabase/auth-helpers/tree/main/packages/sveltekit

I do think checking auth in a server component would likely be better for your use here. Supabase has a nice example here: https://github.com/supabase/auth-helpers/tree/main/examples/nextjs-server-components They have a simple case with Middleware, but you wouldn't need to do it that way. Can use "redirect(/login)" from the server component.