Next.js 13 Full Stack E-commerce App #14 | Error Handling, Custom Error Response
Вставка
- Опубліковано 23 бер 2023
- Git Repo Link:
github.com/ghulamabbas2/buyit...
Checkout my In-Depth Next.js Masterclass on Udemy Courses:
www.udemy.com/course/nextjs-b...
Next.js 13 Authentication with Next-Auth:
• Next.js Authentication...
================================================================
⚙️ Gadgets I use for Recording:
💻 Laptop - Macbook PRO M1 - 16/512
amzn.to/4eUqrSe
🎤 MIC - Samson Technologies Q2U USB/XLR Dynamic Microphone
amzn.to/3W9Z4wl
🖱️Mouse - Logitech G402 Gaming Mouse Hyperion Fury USB, Black
amzn.to/3RY4xUy
⌨️ Keyboard - Logitech K380 Multi-Device Bluetooth Keyboard
amzn.to/3RY4Fn0
🖥️ Monitor - UltraSharp 24-Inch Screen Led-Lit Monitor (U2419H)
amzn.to/4bxidN6
================================================================
Welcome to the 14th episode of our Next.js 13 Full Stack E-commerce App series! In this video, we will be focusing on Error Handling and Custom Error Responses.
Error handling is an essential part of any application, and in this tutorial, we'll show you how to handle errors gracefully in your Next.js app. We'll also demonstrate how to create custom error messages and responses to provide a better user experience.
By the end of this tutorial, you'll be able to handle errors like a pro and provide a smoother user experience to your customers.
If you're new to this series, we highly recommend checking out the previous episodes to get up to speed with everything we've covered so far. Don't forget to subscribe to our channel and hit the notification bell to stay updated with our latest videos.
Thanks for watching, and let's get started!
Thanks, keep up the good work going.
Once more, thanks!!!! Best content!
Glad you enjoy it!
Thanks mr Abass i appreciate this gift
This course is incredible, I've learned with you in the past with django and next. you are amazing.
Glad you enjoy it!
nice work again, thanks
Thanks.
I really appreciate your work on this project. Thank you so much sir.
very nice and thank you for sharing your expertise and knowledge! keep up the good work my man
Around 30-35
U r not using ssr ssg isr csr concept ...why?
Can anybody clarify my doubt
I don't quite get the same error output when I run postman. This is what I am getting
{
"success": false,
"error": {
"statusCode": 500,
"message": "Parameter \"obj\" to Document() must be an object, got "
},
"message": "Parameter \"obj\" to Document() must be an object, got "
}
On which route?
Only next connect can not follow along with the course. Next connect does not work with next 13.4. Other way to protect routes is nexAuth which you do not cover!
Watch this Video:
ua-cam.com/video/eiVBV2fW-aA/v-deo.html