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 🙏

© 2024 – Pkg Stats / Ryan Hefner

express-error-middleware

v1.3.0

Published

Simple error handling middleware for express.js

Downloads

14

Readme

express-error-middleware Build status Coverage status

Simple error handling middleware for express.js

Install

$ npm install --save express-error-middleware

Usage

Below is a example of usage. test/app.js also have a similar example.

var express = require('express');
var errorHandler = require('express-error-middleware');

var app = express()

// define your routes

app.use(errorHandler.NotFoundMiddleware); // if a request is not handled before this a NotFoundError will be sent into next
app.use(errorHandler.ErrorsMiddleware); // this will render an error page based on the error it gets.

NotFoundMiddleware

Creates a NotFoundError and passes it along.

ErrorsMiddleware

Renders a request based on the error. error.status will determine the status code of the HTTP request in addition to selecting the template. If error.status is not set, it will default to 500. The template rendering looks for error/<status-code>. Thus, if jade is the template engine an error with 403 as status code will use error/403.jade as a template.

ApiErrorsMiddleware

Creates a JSON-response with the error, works similar to ErrorsMiddleware in the way that error.status defines the HTTP status code.

CsrfErrorMiddleware

Helper for using csurf. It turns an error from csurf into something that ErrorsMiddleware and ApiErrorsMiddleware understands.


MIT © Rolf Erik Lekang