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

response-catcher

v0.2.8

Published

Easy async error handling in Express

Downloads

2

Readme

response-catcher npm

Easy async error handling in Express

npm install --save response-catcher

Introduction

response-catcher is an extremely flexible .catch() error handler for promise-based express request flows.

It should be used where you would have multiple .then() operations in a request and need to be able to throw and handle many kinds of errors.

By default it attaches itself to res.error() (though this can be configured).

Usage example

const express = require("express");
const app = express();

const responseCatcher = require("response-catcher");
app.use(responseCatcher());

app.get("/", (req, res) => {
	findUser()
		.then(checkUser)
		.then(andThenThisThing)
		.catch(res.error());

	async function findUser() {
		let user = await db.users.find(req.body.id);
		if (!user) throw 404;

		return user;
	}

	async function checkUser(user) {
		if (!user.isAuthenticated) throw [401, "User is not authenticated"];
		else if (user.alreadyExists) throw ["User already exists", 409];
		else if (user.username.length > 8) throw "Username is too long";
		else if (serverErrorSomewhere) throw { status: 500, body: "Sorry, we had an error somewhere!" };
	}

	async function andThenThisThing() {
		// ...
	}
});

Configuration

Instantiation

On instantiation of the middleware function, you can set the following properties (with the listed values being the defaults):

{
	name: "error", // The name of the function to use: "res.error()"
	status: 400, // The default response status to use
	logger: console.log, // The logging function to use for errors
	logging: false // Whether or not to log errors
}

To use a custom logger that isn't console.log, supply it to the logger key. This still won't enable logging, which to do set logging: true.

You can supply as many arguments as you like. Any string you provide will interpreted as the name, any number you use will be interpreted as the status, and any object you use will have the named properties.

const responseCatcher = require("response-catcher");

app.use(responseCatcher()); // Use the default values
app.use(responseCatcher(405)); // Change the default status to 405
app.use(responseCatcher({ logger: console.log })); // Enable logging
app.use(responseCatcher("handleError", { status: 500 })); // Change both the default function name and the status

Creating the error

Coming soon...

Ways to throw an error

Coming soon...