Auth not set on server side with link (magic link) login

Version

@nuxtjs/supabase: v0.1.9 nuxt: v3.0.0-rc.1

Steps to reproduce

Set up a login form using the just the email to receive a magic link

const { session, error } = await client.auth.signIn({ email: email.value })

Use a middleware like this

export default defineNuxtRouteMiddleware((to) => {
  const user = useSupabaseUser()
  if (!(user.value))
    return navigateTo({ name: 'login', query: { redirect: to.path } })
})

What is Expected?

The user should be set on the server side.

What is actually happening?

The token on the server side plugin is null:

export default defineNuxtPlugin(async () => {
  const user = useSupabaseUser();
  const client = useSupabaseClient();
  const token = useSupabaseToken();
  if (!token.value) {
    return;
  }
  const { user: supabaseUser, error } = await client.auth.api.getUser(token.value);
  user.value = error ? null : supabaseUser;
});

Therefore the middleware redirects the user to the login and the user only becomes available after the middleware has run, leaving the user on the login page. A fix would involve watching the user, but thats still leads to the login page shortly showing up before the user is redirected again.

This issue is linked to #28 but singles out the ssr issue when using magic links

[larbish]

Hey @nosizejosh, that’s a way I found to avoid the display of the login form highlited by @mwohlan. That was just a proposition.

[nosizejosh]

Thank you @larbish