Відео

Thanks so much! I’m focused on creating valuable content, and I believe the subs will grow with time. Glad you enjoyed the video!

You can get the upload progress using axios.

yes

Yes. Create an API endpoint which will accept log data and send it to telemetry backends. You will then make an http request from middleware with the data. Api endpoint will recieve the data and send it to correct telemetry backends. This way you can even log things from the client side.

​@@AdityaSinghCodes Thank you. But is there somewhere to read why it doesn't work in middlewares? I thought that instrumentation is executed before middleware.

The instrumentation we are doing in this video depends upon a lot of packages that only works with nodejs runtime. Middleware in next.js runs in edge runtime so that's why we can't use this inside of middleware. However vercel otel works with edge runtime but it has limitations also in terms of what it can log.

​@@AdityaSinghCodes Thank you so much!

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);

Share your code so I can take a look. Message me on X

@AdityaSinghCodes im shared through x

try logging out and then logging in

that depends upon if you need that info. but I guess if you are using promethues, you are most likely interested in server resources like cpu and memory usage and in that case just collecting the default metrics would be fine.

@AdityaSinghCodes thanks for the reply. Amazing content. Looking forward for your next videos. I have a suggestion: Kafka setup for event driven architecture and using in nodejs or nextjs.

Def I have to make videos on kafka

Appreciate the support!

Thank you for the support man.

I’m trying to set up authentication that works across both the Node environment and the Edge environment. I’m using the Prisma adapter, but it’s not compatible with the Edge environment unless you use Neondb or something. So, for the Edge environment, we’ll need to create an authentication instance that doesn’t include the Prisma stuff. This means we’ll have to split the configuration, which will create two authentication instances: one without the Prisma adapter and one with the Prisma adapter. When you’re doing this, make sure you handle any Prisma-related stuff inside your route handlers.

@@AdityaSinghCodes oh I see, that makes sense. Both of the video were fantastic. thanks bro

you are such an amazing person

Splitting the config is only necessary if you are using things that are not supported in edge runtime. For e.g. prisma stuff.

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..

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!

using revalidate with fetch means, the cache is going to be invalidated only for that specific request. but when you use export const revalidate, next.js will invalidate the cache for the entire route.

@AdityaSinghCodes thanks

Awesome. Multi-tenancy is a good idea. I will create a video on this along with custom domain and ssl certificates.

Thanks man. Added the timestamps.

that's great. Docker is really powerful

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 👍

Great

Sure bro. In short, You can add 2 fields. One for token and one for token expiration. Whenever someone signsup, you generate a token, add it as a query param to your email verification url. Create this url and whenever this page gets loaded validate the token. If token is valid, email is verified.

Also send them an email which contains this url.

@@AdityaSinghCodes thanks for replying! i'll try to implement it.

Not in this one. But in the upcoming video

Nope

right

Glad to hear it was helpful!