Custom Error Classes: Beyond Generic Errors
Create specific error types, like `NotFoundError`, instead of generic ones. This lets your code react differently to different failures, like sending a 404 for a missing user vs. a 500 for a database outage.
Think of custom errors as specific labels for what went wrong. Instead of a generic `Error`, throwing a `ValidationError` or `NotFoundError` gives your error handling logic a clear signal to act on, such as returning a 400 vs. a 404 status code. This makes your code more readable and robust by distinguishing between client mistakes and server failures. The main footgun is forgetting to call `super(message)` in the constructor, which breaks the error message and stack trace.
Read the original → developer.mozilla.org
- #javascript
- #node.js
- #error-handling
- #express
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.