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

v1.0.6

Published

A custom error and error middleware solution for Express, written in TypeScript with error types and subtypes in mind.

Downloads

5

Readme

express-error-factory

This is a simple custom error class and middleware for Express to better facilitate error handling in Express.

Usage

Installation

npm install express-error-factory

First, generate the custom errors using the CustomErrorThrower class.

const customErrors = new CustomErrorThrower({
    rodentError: {
        tooManySquirrels: {
            {
                type: "rodentError",
                statusCode: 400,
                message: "The squirrels have chewed all of your cables."
            }
        },
        possumKingdom : {
            type: "rodentError",
            statusCode: 500,
            message: "The opossums have decreed that your realm is now theirs."
        }
    },
    insectError : {
        bees: {
            type: "insectError",
            statusCode: 404,
            message: "Bees?"
        }
    }
})

Errors can then be generated or thrown easily in any Express route.

For synchronous code, use the throwCustomError(errorType) method.

// generates a function to throw 'rodentError' errors 
const thrower = customErrors.throwCustomError("rodentError");

// throws an error with the information in the tooManySquirrels object.
thrower("tooManySquirrels");

For asynchronous code, promises, or try/catch blocks, pass the error generated from the getErrorResponse(errorType) method to the Express next() function. For example:


// generates a function to create 'rodentError' errors
const createError = customErrors.getErrorResponse("insectError");

try {
    fetchDataFromApi();
} catch (error) {
    // do something to narrow error type to determine which custom error to throw
    next(createError("bees"));
}

See the Express documentation here for more information about the difference between syncrhonous and asynchronous errors.

Include the middleware as the last app.use(). The function can be given a custom error message for uncaught errors not specified in the CustomErrorThrower class.

app.use(authenticationMiddleware);

app.use(route1);
app.use(route2);

/*
.
.
.
*/

const errorMiddleware = handleCustomError("Uncaught Error Message");

app.use(errorMiddleware);

Github