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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@erangamadhushan/express-advanced-error-kit

v1.6.0

Published

Advanced TypeScript error handling middleware for Express applications.

Readme

@erangamadhushan/express-advanced-error-kit

Advanced TypeScript-based error handling middleware for Express.js.

npm version npm downloads


✨ Features

  • Async handler wrapper
  • Custom ApiError class
  • Predefined error classes (NotFound, BadRequest, etc.)
  • createError helper for clean DX
  • Global error middleware
  • 404 Not Found middleware
  • Logger integration (Pino, Winston, custom)
  • MongoDB duplicate key smart parsing
  • Zod validation error formatting
  • Standardized error response structure
  • Production-safe stack handling
  • ESM + CommonJS support
  • Full TypeScript support

📦 Installation

npm install @erangamadhushan/express-advanced-error-kit

🚀 Quick Start

import express from "express";
import {
  asyncHandler,
  createError,
  notFoundMiddleware,
  errorMiddleware,
} from "@erangamadhushan/express-advanced-error-kit";

const app = express();
app.use(express.json());

app.get(
  "/users/:id",
  asyncHandler(async (req, res) => {
    if (req.params.id !== "1") {
      throw createError.notFound("User not found");
    }

    res.json({ id: 1, name: "John" });
  }),
);

app.use(notFoundMiddleware);
app.use(errorMiddleware());

app.listen(5000);

🧠 Recommended Workflow

  • Wrap all controllers using asyncHandler
  • Throw errors using:
    • createError.* (recommended)
    • or ApiError
  • Use global errorMiddleware
  • Integrate logger in production

🧩 Error Creation Options

Using createError (Recommended)

throw createError.badRequest("Invalid input");
throw createError.notFound("User not found");
throw createError.unauthorized();

Using ApiError

throw new ApiError("User not found", 404, "USER_NOT_FOUND");

Using Predefined Classes

import { NotFoundError } from "...";

throw new NotFoundError("User not found");

📤 Response Format

All errors follow a consistent structure:

{
  "success": false,
  "statusCode": 404,
  "message": "User not found",
  "error": "NotFoundError",
  "code": "NOT_FOUND"
}

🧠 Smart MongoDB Error Handling

Duplicate key errors are automatically formatted:

// Mongo duplicate key error
{
  code: 11000,
  keyValue: { email: "[email protected]" }
}

Response:

{
  "success": false,
  "message": "email already exists",
  "code": "DUPLICATE_FIELD"
}

🧾 Zod Validation Formatting

If using Zod:

throw new ZodError([...]);

Response:

{
  "success": false,
  "message": "email: Expected string",
  "code": "VALIDATION_ERROR"
}

🪵 Logger Integration

Use any logger:

import pino from "pino";

const logger = pino();

app.use(
  errorMiddleware({
    logger: logger.error.bind(logger),
    showStack: false,
  }),
);

📚 Middleware Order (Important)

app.use(routes);

app.use(notFoundMiddleware);
app.use(errorMiddleware());

🧩 Creating Custom Errors

🔹 Using createError (Recommended)

import { createError } from "@erangamadhushan/express-advanced-error-kit";

throw createError.notFound("User not found");
throw createError.badRequest("Invalid input");
throw createError.unauthorized();

🔹 Using ApiError

import { ApiError } from "@erangamadhushan/express-advanced-error-kit";

throw new ApiError("User not found", 404, "USER_NOT_FOUND");

Also You can extend it:

import { ApiError } from "@erangamadhushan/express-advanced-error-kit";

class ValidationError extends ApiError {
  constructor(message: string) {
    super(message, 400, "VALIDATION_ERROR");
  }
}

⚙️ Configuration Options

errorMiddleware({
  logger?: (error: any) => void;
  showStack?: boolean;
});

🛡 Production Behavior

  • Stack traces hidden automatically in production
  • Clean JSON response format
  • Centralized error control

🧪 Testing

npm test

🔄 Automated Releases

  • Conventional commits
  • semantic-release
  • GitHub Actions CI
  • Automatic versioning and changelog generation