Not only helped with JS error handling, but was a great introduction to error handling abstraction in general. This was a huge help!

Really great video. Clear, concise, fast. Just how I like it. subscribed!

The flow of your explanation just makes each step of the tutorial fall into place instantly. Thanks a lot!

This is the best error handling tutorial I have watched. Thanks

Very straightforward explanation, thanks!

This video is really helpful and straightforward. I can now know what’s wrong with my project properly 😂

Thanks I really watched many tutorial about this topic but none was like yours. Thanks sir 💯💯

I just came across a similar implementation in an old project at work, shame I didn’t watch this before then, it would’ve helped me a lot. Awesome video!

This is the most beautiful way i have seen 😮. Thanks so much.

Super excellent video that really helps me a lot during refactoring the node project!! Thank you so much😃

Very well explained 👍. Thanks man.

Great video man! Keep up the good work and it will pay off! Thanks for the knowledge.

@nikita-dev

Жыл бұрын

thank you!

Thanks bro! This was really helpful, please keep uploading

You will definetely going to become a successful youtuber Just keep uploading Regularly !

As someone who is learning Node and finished with the basics of mongoDB & mongoose, error handling was still a little unclear to me. This helped out massively, thank you! earned a sub.

@mma-dost

Жыл бұрын

Same bro I was not able to clearly understand error handling.

@rohanshrestha8302

Жыл бұрын

@@mma-dost Hey bro can you suggest some sites or mentors you followed to learn node

You earned a sub man. What a fantastic video.

Thx a lot for this simple and efficient tutorial

bro please keep these quality videos coming. please

Error handling strategies was unclear for me like the "this" keyword. tnx for giving us ideas regarding on effective error handling. keep it up ❤

Great job! 👏 Keep it up!

Amazing tutorial ❤

Lastly I found right one❣️

Wow, thanks man! great video!!

You helped me a lot. Thank you so much.

To the point. Subscribed👍👍

very clearly explained.

thank you, very helpful

I have 4 years experience and i was handling errors inside the controller...this is more Clear

Awesome bro... panda gang op

Helpful video❤

Great content!

Amazing

really great bro . respect++

very helpful

Hello! Thank you for the video! Is this the correct way to handle errors for a production environment ? I've read its a good approach to add graceful shutdown. What do you think ? and where or when should we add this ?

Thanks man!

New subcriber

super!

Please which extension are you using ? The grey intellisense, seems like tabnine but i guess it's not

Hello there, I am kind of new to node, and as I'm learning all the videos seem to focus just on file read and write, events and http request, it that all of it in node, as documentation is not similar to laravel, it is a bit hard for me to switch please help

How do you export the actual AppError class and use it in those other files? You don't seem to do that but I'm having to do module.exports for that class then importing it in the other files??

@nikita-dev

4 ай бұрын

I'm exporting the AppError class by doing: module.exports = AppError; then importing it by doing: const AppError = require("./AppError"); I have a video about Node JS module imports/exports if you want to learn more about how this works!

@MrGangel77

4 ай бұрын

@@nikita-dev cheers. I emailed u too :P

Thankssssssssssssssss

Why do I need to throw an error and then catch it? I mean if !user then return next(error); Is there any benefit or throwing and catching again?

@nikita-dev

Жыл бұрын

Great question! The benefit is that all of your error handling code will be in one place -- the error handler middleware -- and it will reduce repetition. If you were to send the error response in your controllers (instead of passing the error on), you would have to write "res.status(400).send(msg)" every time. Once your routes become complex and there are multiple different checks, you would be repeating yourself a lot. It's much cleaner to just pass the error on to the error handler middleware, and then define the error response there (once).

@mma-dost

Жыл бұрын

thanks for asking the doubt bro I was also used to think why not just send res.json(error).status(400) like that.

How about to write tryCatch function in such form: exports.tryCatch = fn => (req, res, next) => fn(req, res, next).catch(next); Looks cleaner

I had to dislike this video, the explanation was good but you covered Express error handling, not Node. By that I mean the ones which crash the node server.

Perfect explanation!

@nikita-dev

Жыл бұрын

thank you!

super!