Being new to Remix AND Supabase, I've been tripping over a lot of little things getting started with all of this put together. Watching this video, I can tell it's really thoughtfully crafted to cover all those little things! Thank you, this is really well done.
I just completed the egghead course and finished this video too and, isn't better to just use auth in the server with the server client and actions instead of syncing the client and the server?
I'm thinking the same thing! and it's more than better, it's required. you must validate the data. But then, the client will not be synched, since .onauthstatechanged() will not trigger the events (since you do that in the server and not the client), but now, how do you synch the client then ??
If you follow the good old remix pattern, you won’t need to revalidate the client because you'd fetch the data from a route loader and if you change something you would mutate the data with an action, and as you know after every action the loader is called back again. So no need to sync the client
Sorry coming late to this. Well spotted and I started to reason the same way but then aren't the supabase auth methods client only functions? How would you go about calling them from an action?
when you created new supabase client at the root file, have you imported that client to the dashboard file? or does dashboard file still maintains its separate client as you should in the beginning? this part was not obvious in the video
cmiiw: those buttons live in client, while /dashboard that render the data live inside server. one more thing: how to handle error? I think this is important.
Yeah I was getting non-stop rerenders, however I still get a another 4 fetch calls, two of which are cancelled, after moving then coming back to the window from another tab - really weird.
Being new to Remix AND Supabase, I've been tripping over a lot of little things getting started with all of this put together.
Watching this video, I can tell it's really thoughtfully crafted to cover all those little things! Thank you, this is really well done.
I was just searching for remix supabase auth!!! glad to see this video made by Supabase itself🎉
Awesome! Glad you found it! 🙌
I came to TH-cam just on the off chance that something like this existed but without any hope that it would! And here it is!
so 6:00 you created a supabase client in dashboard.tsx and then another client in root.tsx 8:28 ?
You guys have made it SUPA easy. :D
That was the goal! ⚽
Can we get a new video using the ssr package?
please! omg Im struggling so hard
Very useful and clear video!!! thanks
Glad you enjoyed it! 🙌
I just completed the egghead course and finished this video too and, isn't better to just use auth in the server with the server client and actions instead of syncing the client and the server?
I'm thinking the same thing! and it's more than better, it's required. you must validate the data. But then, the client will not be synched, since .onauthstatechanged() will not trigger the events (since you do that in the server and not the client), but now, how do you synch the client then ??
If you follow the good old remix pattern, you won’t need to revalidate the client because you'd fetch the data from a route loader and if you change something you would mutate the data with an action, and as you know after every action the loader is called back again. So no need to sync the client
@@diurivj yes, that's true. there's a GET request after every action trigger.. yeah then, I don't see a reason why not doing auth on the server..
Then you will have to send session manually along with the response, right?
Sorry coming late to this. Well spotted and I started to reason the same way but then aren't the supabase auth methods client only functions? How would you go about calling them from an action?
At 11:30 I see signing in and out changes in cookies, not local storage.
when you created new supabase client at the root file, have you imported that client to the dashboard file? or does dashboard file still maintains its separate client as you should in the beginning? this part was not obvious in the video
lol nice one getting the database dot new domain!
Great guide
How to use supabase with prisma, in currently using sqlite in remix app
Why isn’t auth handled via an action?
cmiiw: those buttons live in client, while /dashboard that render the data live inside server.
one more thing: how to handle error? I think this is important.
if anyone is getting rerendering because of useeffect, removing revalidator from dependency array solves the issue
Thanks for that comment. Do you have further explanation?
Yes - I'm seeing the exact same thing. Thanks.
Yeah I was getting non-stop rerenders, however I still get a another 4 fetch calls, two of which are cancelled, after moving then coming back to the window from another tab - really weird.
okay done subscribe, hopefully my code will work
In current version of the Remix, I got infinite loop of re-render. I fixed used this way, might help someone!
const { ENV, user } = useLoaderData();
const navigation = useNavigation();
const revalidator = useRevalidator();
const [supabase] = useState(() =>
createBrowserClient(ENV.SUPABASE_URL!, ENV.SUPABASE_ANON_KEY!)
);
useEffect(() => {
const {
data: { subscription },
} = supabase.auth.onAuthStateChange((_event, session) => {
if (session?.user.id !== user?.id) {
revalidator.revalidate();
}
});
return () => {
subscription.unsubscribe();
};
}, [supabase, revalidator, user]);
Are you able to get this auth flow to work with email/password sign up instead of oath?