Don't Try Catch These Next.js Errors 

For the recent few days I have been having the WORST TIME of my dev life with this weird error. Your explanation cured my (metaphorical) cancer! Thanks a lot!

That's seems to me like a bad API design in Next.js

I was doing the exact same pattern of abstracting the db queries is a separate function and calling that function from the server action and getting that error. Very good video!

Hi , I want to learn about AWS (EC2,S3 , lambda) and their integration with React application. So from where I can learn these efficiently.

Hi. It's me again :)))) I think comments for youtubes affect positively on your channel! 😇❤ Could you please make the following video: example of user authorization, registration, user roles. Please use nextjs 14, typescript, server actions, nextauth 5, prisma, shadcn ui, react-hook-form, zod, sonner. Have a nice day 😘

great video, pretty mindblowing!

Thanks for the very informative video! I had this issue and didn't realize it. It was causing an error to pop up during my authentication flow, which I was planning to investigate but hadn't gotten around to yet. You probably saved me hours of racking my brain. Thanks!

This is a reason I'm still coding in react with the react router dom.

I love your videos, please do keep going

Wow thats actually wild, I had no idea😮

Really nice video, I dont know this, thanks a lot

Well broken down

amazing video

I don't know why you have not attached your lib, but I've found it (might-fail) and tapped a star in github. Thank you!

great video

Had an error where my code always failed when I wrapped my redirect with a try catch. struggled with it for a few hours before realizing the try catch being there was the problem

Let's just re-throw it if its a NEXT_REDIRECT :')