Baptiste Leproux

After digging a lot in sub dependencies, I finally found the guilty. I'll soon provide a release to fix it. To fix it temporary, can you try to add a...

You can now remove the temporary fix, this issue should be fixed on `v0.1.18` thanks to #55 and should also be fixed on other version thanks to [mlly update](https://github.com/unjs/mlly/commit/896c8a7dd087d041ffb29a00065a4f71d62ed249). Thanks...

I have no choice, the Supabase `onAuthStateChange` event is sent on client side. Once the event is received, it shares the data between server and client. Until then, the server...

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 Please refer to my [response](https://github.com/nuxt-community/supabase-module/issues/32#issuecomment-1108613374). Auth state changes are monitored and synced with server (you can check the [code](https://github.com/nuxt-community/supabase-module/blob/main/src/runtime/plugins/supabase.client.ts#L23)) but the supabase event is fired on client side. You...

Hey @ColinEspinas, can you please provide a reproduction ? I did not manage to reproduce it using supabase magic link (is it what you called "sign up confirmation link" ?)

@ColinEspinas Can you please update to the last version of the module (`0.1.8`) ? I tried on your repo, it was ok for me. Let me know !

The tag was available anyway. Just created the release 😀

@ColinEspinas Are you using the latest nuxt3 version ?

Thanks for the help @thorwebdev. We're listening on the `onAuthStateChange` event and calling the API route on change: https://github.com/nuxt-community/supabase-module/blob/main/src/runtime/plugins/supabase.client.ts#L23