Nodejs Error Handling in Production: What You're Doing Wrong (2024)

Показать описание

Here is the source code link along with the workflow files:

If my effort is helping you! You can buy me a Coffee:

Previous Episodes:

Microservice source code:

Рекомендации по теме

Комментарии

The way you explain complex concepts with such clarity and enthusiasm has not only made advanced topics accessible but also incredibly engaging. Your content has provided me insights and skills that are essential for our growth and development👌.

huzaifaasif

Oh how I waited for this video! Thank you so much for making it! :)

talkohavy

Thank you for this series. keep up the good work.

varileshtlesht

Can you put a link of all the diagrams that you draw ? 🙂 it will be very helpful . thank you for your hardworking . good luck !!

manothmc

Hi Jay, once again thanks for this good series. Would u mind guiding us what's your thought process when dividing/spliting the microservices? For example, what should our mind be thinking when we are designing and dividing the microservices.

weijiephua

Thank you for this wonderful series Jay ! Also do you have source code of a version of this project with minimal frontend within it?

Aditya-xede

Hi Jay,
I just finished watching the video in full and I have a follow-up question.
Should each micro-service handle its own errors? Or should there be like some Global middleware that all micro-services share?
What is the best practice on that?

talkohavy

hi Sir, how can i run this project with frontend when i download from your github

HaoBui-tfbv

hi jay, first thank you for nice lecture .
i have a question. the question is
[NotFoundError, ValidationError, AuthorizeError].forEach((typeofError)=>{
console.log(error instanceof typeofError);
if(error instanceof typeofError){
console.log(typeof typeofError);
reportError = false;
}
});

this code capture whether the 'error' is instance of 3 classes. but 'error' is an object and [notfound, validation, authroize] are classes.
i think this code is not working properly. is it right ?

shy-soonyubing

You're coupling http concern in your Service by throwing those errors which contain an HTTP status code. Why? The Service defines the business logic and the handler defines the HTTP concern.

mroobert

Nodejs Error Handling in Production: What You're Doing Wrong (2024)

Nodejs Error Handling in Production: What You're Doing Wrong (2024)

#95 Development & Production Error | Error Handling in Express | A Complete NODE JS Course

How to handle Node.js errors like a Pro?

#91 Global Error Handling Middleware | Error Handling in Express | A Complete NODE JS Course

Error Handling in NodeJS (Complete Guide) | Node Tutorial

Express JS Mistakes Every Junior Developer should Avoid | clean-code

Error Handling in Express

Central Error Handling In NodeJS and TypeScript

#02 Setting up Development Environment | Nest JS Project & Modules | A Complete Nest JS Course

Async error handler using express.js

#100 Handling Uncaught Exceptions | Error Handling in Express | A Complete NODE JS Course

Hate Try...Catch Error Handling in Node.js? Do This Instead

Express server error handling

#92 Creating a Custom Error class | Error Handling in Express | A Complete NODE JS Course

Better Application architecture with Error Handling | Expressjs

NodeJS : Error handler ignored when NODE_ENV=production

Production grade logger in Javascript | Winston

JavaScript Error Handling and Tracking Tips and Tricks

Jake Verbaten: 'Node.js Error Handling'

Error handling with error middleware | Express JS & Node JS

JavaScript Fetch API - One Mistake I ALWAYS MAKE!

#12 - Global Error Handler | Complete Node JS Production Setup | JavaScript | TypeScript #coding

SFNode Meetup: Robust Error Handling in Node.js Applications - Lewis Ellis - 2017-03

#98 Handling Mongoose Validation Errors | Error Handling in Express | A Complete NODE JS Course