Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Simple error handler middleware for express

tree: 25e96b8ea4

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 http
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 index.js
Octocat-spinner-32 package.json

build status

Express errors

Available in NPM npm install express-errors

Provides easy access to common http errors for express e.g.

  • 400 - Bad request
  • 401 - Unathorized
  • 403 - Forbidden
  • 404 - NotFound
  • 409 - Conflict
  • 500 - Internal server error


You need create views/errors directory and add 401,403,404 error views.

    var logger;
    app.get('/400', function(req, res, next){
      next(errors.BadRequest); // You will get "bad request" error

    app.get('/500', function(req, res, next){
      next(new Error('Something went wrong :(')); // You will get "Internal server error" error

    var errors = require('express-errors');

    logger = function(err){ // Custom logger function
    errors.bind(app, { layout: false, logger: logger }); // IMPORTANT! Call it after all routes ready


Currently this options are available:

  • lastRoute - if false express-errors will not maintain last app.use route(NotFound error)
  • plain - if app.settings['view engine'] is undefined OR this option is presented res.send instead of res.render will be used
  • logger - custom logger function

Defining an error

Yeah, you can. Use .define method:

      name: 'BadRequest', // You will be able to access it through `errors.BadRequest` in future
      message: 'Bad request', // This message for XHR requests
      status: 400 // HTTP status


  • More options
Something went wrong with that request. Please try again.