Chapter 4. Errors and Debugging
In Node, error objects are important. They are used to communicate the existence of problems and provide context and details about them. Good handling of errors makes programs more reliable and secure.
This chapter is all about errors and how to deal with them. We’ll first talk about throwing and catching errors and then discuss the different types of errors and what layered error management looks like. We’ll then explore debugging Node code and discuss some preventive measures that we can use to reduce potential errors.
Throwing and Catching Errors
An error in Node is an object instantiated from the Error class. Sometimes you’ll need to create your own error objects, like this:
consterror=newError('Some message');
This is a generic error object, which is not something you should ever use, as there is a better option that we’ll discuss shortly. Node also has built-in errors, which are basically error objects already created for you. The next section covers those.
What exactly do you do with an error object? Well, regardless of the type of error and whether you created it or it was built-in, whenever you’re in a place in the code where a condition should not happen, you need to signal the details of that problem to whoever is using your code. You can do that by throwing the error.
For example, let’s say we want to create a function to calculate the square root of a number. One restriction such a function should have is to block any operation ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access