Making our way through the twists and turns of our full Node.js Error Handling series, today we’ll be checking out the SyntaxError in Node. As with nearly ever other programming language on the market, a Node SyntaxError indicates that a code statement could not be correctly parsed, which means that… continue reading →

Moving along through our detailed Node.js Error Handling series, in today’s article we’ll be checking out the ReferenceError in all its glory. If you’re familiar with plain JavaScript ReferenceErrors, the ReferenceError class in Node will look quite familiar, since it performs the same role: When a reference is made to… continue reading →

Continuing along through our in-depth Node.js Error Handling series, today we’ll be going over the RangeError. As with many other programming languages, including Ruby with the RangeError article we covered in that language, the Node.js RangeError is thrown to indicate that a passed function argument does not fall within the… continue reading →

Starting off into our detailed Node.js Error Handling series, today we’ll be going over the AssertionError. As with many other programming languages, Node.js comes with an assert class as part of its core modules set, allowing simple assertion tests to be performed. When such an assertion fails an AssertionError is… continue reading →

The Node.js error class hierarchy consists of about half a dozen unique classes, most of which inherit from the baseline Error class. A Node.js application will typically experience errors that fall into one of four categories: Standard JavaScript errors like RangeError, ReferenceError, and TypeError. System-level errors from the underlying operating… continue reading →