npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

dynamic-error-handler

v1.0.1

Published

A clean, dynamic Express error handler middleware with AppError class and centralized logging.

Readme

Dynamic Error Handler

A clean, modular, and dynamic Express error handler middleware with centralized logging and custom error class — written in TypeScript. Handles common errors like CastError, ValidationError, MongoDB duplicates, JWT errors, and more.


Features

  • ✅ Custom AppError class for operational errors
  • ✅ Dynamic error handler middleware with extensible error handling
  • catchAsync helper to wrap async route handlers and forward errors
  • ✅ Centralized error logging to logs/error.log (configurable)
  • ✅ Clear JSON error responses for both development and production
  • ✅ Toggle detailed logging with a simple flag
  • ✅ TypeScript-ready

Installation

npm install dynamic-error-handler

Usage

Basic Setup

import express from "express";
import {
  AppError,
  createErrorHandler,
  catchAsync,
} from "dynamic-error-handler";

const app = express();

app.get(
  "/test",
  catchAsync(async (req, res, next) => {
    // Simulate an async error
    return next(new AppError("Something went wrong!", 400));
  })
);

// Use the error handler middleware after all routes
app.use(
  createErrorHandler({
    logErrors: true,
    MyCustomError: (err: any) =>
      new AppError(`Custom error: ${err.message}`, 400),
  })
);

app.listen(3000, () => {
  console.log("Server running on port 3000");
});

API

AppError

Custom error class extending the built-in Error class.

new AppError(message: string, statusCode?: number)
  • message: Error message string
  • statusCode: HTTP status code (default: 400)

catchAsync

Wrap your async route handlers to automatically catch errors and forward them to the error handler.

const catchAsync =
  (fn: (req: Request, res: Response, next: NextFunction) => Promise<any>) =>
  (req, res, next) => {
    fn(req, res, next).catch(next);
  };

createErrorHandler(options?)

Express error handling middleware. Use at the end of your middleware stack.

  • options (optional):

    • logErrors (boolean): If true, errors are logged to logs/error.log and console (default: false).

Example:

app.use(createErrorHandler({ logErrors: true }));

Supported Error Types

  • CastError (Mongoose invalid IDs)
  • ValidationError (Mongoose validation)
  • MongoDB duplicate key errors
  • JWT errors (JsonWebTokenError, TokenExpiredError)
  • Other unknown errors are handled gracefully

Logging

  • Logs are appended to logs/error.log in your project root.
  • If logErrors option is enabled, errors are printed to console and saved in the log file.
  • If disabled, logging is suppressed.

Development & Production Modes

  • In development mode (NODE_ENV=development), full error stack and details are sent in JSON response.
  • In production mode, only trusted operational errors show details; otherwise, a generic message is sent.

License

MIT © Ankit Kumar


Contribution

Feel free to open issues or submit pull requests!


Acknowledgments

Inspired by best practices in Express error handling and TypeScript utilities.