Closed laubonghaudoi closed 1 year ago
You probably have a outdated lock file. Update your lock file and try again, also are you able to replicate this locally? It would be good if you could provide a minimal repo with this issue so I can test it locally and deploy to vercel to see this too.
Hi @silentworks , yes I have updated my yarn.lock
file but the issue still persists. I just created a minimal repo:
https://github.com/laubonghaudoi/supabase-auth-bug
I deployed it to vercel using my supabase db. Here is the root url: https://supabase-auth-bug.vercel.app/
And when I go to https://supabase-auth-bug.vercel.app/account which is the auth ui, it gave the same error:
I suspect that this is a Next 13 related. Because I didn't have this issue when I was using Next 12. This happened only after I migrated to Next 13.
Also I am using Mantine UI, not sure it would have any conflicts too.
Any updates here?
https://github.com/supabase/auth-ui/issues/45 this just-merge package is the one causing this i reverted to previous version where it was using lodash and it works fine :)
Hi @sagarchoudhary96 , do you mean that this is introduced from https://github.com/supabase/auth-ui/pull/57 ? This is added in 0.2.4, so I should downgrade it to 0.2.3 instead?
yes, it works with that just downgrade to 0.2.3. i will try to raise a PR to fix the same.
This should be fixed now in the latest 0.2.6
version.
Just upgraded and verified that the error is gone. Thanks!
Bug report
I am using @supabase/auth-ui-react with Nextjs 13, and when I deployed my app to Vercel and went to the auth page, it gave me an client-side error like the screenshot shows below.
Application error: a client-side exception has occurred (see the browser console for more information).
I got no error when developing locally with
yarn dev
, and no error whenyarn build
either. It only occurs when deployed to Vercel. Is this a bug related to Webpack?Screenshots
I clicked into the file prompted by the last line of error
at MessagePort.T (framework-3b5a00d5d7e8d93b.js:33:1904)
and it seems like Webpack-related.System information