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-response

v1.0.6

Published

Contains an expressjs middleware and a tool to throw errors with response codes

Downloads

34

Readme

express-error-response

Error utility and catching middleware for HTTP errors in expressjs

Installation

$ npm install express-error-response

Usage

express-error-response exposes a function which can be called to generate an error handling middleware for expressjs. It adds specific handling for RequestErrors, which are accessible via a property of the exported function.

RequestError

Class that inherits Error. Accessible via the RequestError property of the exported function. The constructor can be called with 2 parameters:

|Param|Type|Description| |-----|----|-----------| |statusCode|string \| number|The status code to be set for the response. This can be either '404' or 404 or notFound. Strings will be parsed and attempted to resolve. If unable to resolve, the status code will default to 500. The status codes either use a parsed number (which may not be NaN, -Infinity or Infinity) or the resolved code, which can be looked up in the statusCodes property of the exposed function. This can also be expanded if necessary.| |body|string \| object|The body to be set for the response. This can either be a string or an object. Depending on how this is planned throughout your application, make sure you set the json property of the middleware appropriately.|

Middleware

The exposed function accepts one parameter called config which can contain the following properties:

|Param|Type|Description| |-----|----|-----------| |logger|function|Any function that is called with the error object. If not passed or not a function, it is silently ignored.| |json|boolean|If the error contains the body property, it will be added to the body of the response. true will respond in JSON, false will respond with a string. Default: true| |catchAll|boolean|Is this the only error middleware, should it catch all errors? Setting this to true will set the status to 500 for every error that is not a RequestError. Default: false| |endRequest|boolean|Should the request be ended after this middleware? true will end the request after setting the status code. Default: true| |defaultFail|Mixed|Any value to respond wiht by default if the error is not a request error, or does not have a body property in general. Default: {} if config.json === true, '' if config.json === false|

Sample

const express = require('express');
const err = require('express-error-response');
const {RequestError} = err;

const config = {
    logger: function(err){
        console.log(err)
    },
    json: true,
    catchAll: false,
    endRequest: true
};

const middleware = err(config);

const server = express();

// Apply your routes and middlewares
server.use('/', function(req, res) {
    throw new RequestError('badRequest', {msg: 'Your request was invalid', info: 'some other info'});
});

// Register the error middleware
server.use(middleware);

server.listen(3000, '0.0.0.0');