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

error-middleware

v5.2.0

Published

More control to express errors

Readme

Error Middleware for Express

build status Coverage Status

This package handles errors on the express code and returns it with a fixed pattern, without leaks. It works with syncronous and asyncronous route functions.

Installation

npm install error-middleware or yarn add error-middleware


Error Types

Currently the middleware has exposed the following error types:

  • BadRequestError
  • ForbiddenError
  • NotFoundError
  • UnauthorizedError
  • Validation Error

But you can also use

  • CustomError

Error response format

The consumer will receive a JSON object with code, type and error as folows:

{
  code: <error code>,
  type: <error type>,
  error: <error message>
}

Example of expected responses

How to use

  • src/index.js Where you declare all your high level routes. The middleware should be last to be able to catch all errors.

    import errorMiddleware from 'error-middleware'
    import routes from './routes'
    
    router.use(routes)
    
    router.use(errorMiddleware)
  • src/routes.js

    import { BadRequestError, ValidationError, NotFoundError } from 'error-middleware/errors'
    
    router.put('/user/:id', (req, res) => {
      const { id } = req.params
      const { name, email } = req.body
    
      const idRegex = /^\d{4}$/
      if (!idRegex.test(id)) {
        throw new BadRequestError(`User 'id' is malformed.`)
      }
    
      if (!validate(name, email)) {
        throw new ValidationError({
          name: 'Name should be at least 4 characters long',
          email: 'Invalid email',
        })
      }
    
      // your update logic goes here
      // { ... }
    
      res.sendStatus(200)
    })
    
    router.get('/error', (req, res) => {
      // an endpoint that simulates a pure error being thrown. It will be translated to InternalError and all its content will not be leaked.
      throw new Error('Internal error that should not be leaked.')
    })
    
    // If no matches found, return 404
    router.use((req, res) => {
      throw new NotFoundError()
    })

Check examples for more