Hey guys. In the video navbar is a server component which depends upon request time information to get the session. This causes all the routes to become dynamically rendered. To fix this, just convert the navbar component to a client component and access session on the client side. I already pushed the code to github repo. Thank you @codezyraofficial for pointing this out.
Hi Aditya, great video. I would recommend adding timestamps/sections. Algorithm will boost the video and it would help people find what they are looking for.
Greate video but just one thing to add , you can use the useSession hook to get the session in client components without the need for a server component , it is wrong in their docs to mention the await auth.api.useSession while it is mentioned in the nextjs integration on client components you can just call the useSession hook which run fine in the client the only caveat is that this will get the seesion is the user logged in also on client side , but if the user logged in server side (eg.server action ) the session will be null .
how do i verify if a user has an account in my client side before i sent the reset password link email? i keep getting the success message eventhough i enter a non existing account
@ ya but i am getting the success toast message without reset password link even the account doesn't exist, my concern is about the toast message, how do I control it
@@AdityaSinghCodes I am getting oauth error message like account is already used in other provider. When I try to log in browser console. Its empty. Can you help me how can I display it in client side.
Hi, thanks for your comment! I try to give enough context while keeping things clear, and most viewers like this approach. I know my videos won’t suit everyone, and that’s okay. If you have specific suggestions, let me know. Otherwise, feel free to check out other content that fits your style better. Thanks for watching!
@@Henok-qn6nc open auth is comparatively very new if you working with hono or something else stuff is not there but it's very easy to implement or I can say free clerk
Hey guys. In the video navbar is a server component which depends upon request time information to get the session. This causes all the routes to become dynamically rendered. To fix this, just convert the navbar component to a client component and access session on the client side. I already pushed the code to github repo.
Thank you @codezyraofficial for pointing this out.
Hi Aditya, great video. I would recommend adding timestamps/sections. Algorithm will boost the video and it would help people find what they are looking for.
Thanks man. Added the timestamps.
Brother you deserve millions subs
thank you so much you are such an amaizing teacher 😃
you are such an amazing person
Thank you for the video,been working on better-auth,it decent.
Please make more on organisation or multi tenet if possible
Awesome. Multi-tenancy is a good idea. I will create a video on this along with custom domain and ssl certificates.
Neat and clean explanation as always 🎉
Greate video but just one thing to add , you can use the useSession hook to get the session in client components without the need for a server component , it is wrong in their docs to mention the await auth.api.useSession while it is mentioned in the nextjs integration on client components you can just call the useSession hook which run fine in the client the only caveat is that this will get the seesion is the user logged in also on client side , but if the user logged in server side (eg.server action ) the session will be null .
Nice vid
Thanks for sharing I am using it it's so easy to implement.
better-auth much better then next-auth
how do i verify if a user has an account in my client side before i sent the reset password link email? i keep getting the success message eventhough i enter a non existing account
It is only going to send reset password email if the email exists in your db
@ ya but i am getting the success toast message without reset password link even the account doesn't exist, my concern is about the toast message, how do I control it
I have not tried this, but try looking in the data when you call forgetPassword. const { data, error } = await authClient.forgetPassword(yourOptions);
Nice video but can you help me to handle error when account linking is false.
what error are you getting ?
@@AdityaSinghCodes I am getting oauth error message like account is already used in other provider. When I try to log in browser console. Its empty. Can you help me how can I display it in client side.
You will get the error info in the query param. Read from there and show the user on the client side.
localhost:3000/sign-in?error=account_not_linked
@@AdityaSinghCodes thanks for help..
idk, i get 401 unauthorized as admin :(
try logging out and then logging in
oh man, this video could really be shorter if you didn’t overcomplicate every simple thing
Hi, thanks for your comment! I try to give enough context while keeping things clear, and most viewers like this approach. I know my videos won’t suit everyone, and that’s okay. If you have specific suggestions, let me know. Otherwise, feel free to check out other content that fits your style better. Thanks for watching!
Actually m confused b/w next-auth and better-auth which one is best ?? What do you think?
Better Auth all the way
Anchi mirt 🎉@@Henok-qn6nc
@@Henok-qn6nc open auth is comparatively very new if you working with hono or something else stuff is not there but it's very easy to implement or I can say free clerk
@@prashlovessamosa It is new. But Its also stable and ready to use on prod. And there is hono integration guide on the documentation. Check that out
@@Henok-qn6nc I am sorry I had no idea about that I will check 👍