Library Philosophy
The philosophy of the library is divided into two main parts:
- What should happen to errors throughout their entire handling lifecycle.
- The library's zero dependency policy.
Error Handling Philosophy
The library was initially created to simplify the handling of various errors that can occur in an Express.js application. Over time, the idea evolved beyond simply handling these errors to also deciding what should happen after they occur.
For example, for errors such as unhandledRejection, the library provides a mechanism for safely shutting down the application.
In my view, an error should be caught, identified, handled, or followed by a proper shutdown.
Zero Dependency Policy
The library was intentionally developed with zero dependencies to avoid supply chain risks and related issues.
I believe that if a library can be implemented without additional dependencies, it is better to do so. Every additional dependency introduces another potential source of hidden or unexpected problems.
For this reason, during the development of ds-express-errors, it was decided that package.json would contain exactly zero dependencies, both at the beginning of the project and in the future.
Start now
Get started with ds-express-errors today through some of these useful resources:
Installatidaon
Add ds-express-errors to your project.
Integration
Learn how to integrate ds-express-errors to your project
Library Mascot
Meet the Devourer of Stacktraces. DS for short.
He eats all handled errors. Don't worry, they're in good hands.