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

@josephdaw/error-handler

v1.2.2

Published

a custom error handler for a node.js and express application.

Downloads

66

Readme

Error Handler

npm (scoped) GitHub Node.js CI Contributor Covenant

Table of Contents

Description

A custom error handler for a node.js and express application.

Installation

Using npm

npm install @josephdaw/error-handler

Usage

Importing

const { errorhandler, CustomError} = require('@josephdaw/error-handler');

Basic Usage

In your express application, add the error handler as the last middleware.

const errorhandler = require('@josephdaw/error-handler');
const express = require('express');
const app = express();

// ... other middleware

app.use(errorhandler());

Using with a Custom Logger

You can pass a custom logger to the error handler. The logger must have a log method that accepts a string. In the example below, we are using a custom logger package. You can create your own custom logger, or just pass in a generic logger such as winston or pino.

const logger = require('@josephdaw/logger');
const errorhandler = require('@josephdaw/error-handler');
const express = require('express');
const app = express();

// ... other middleware

app.use((err, req, res, next) => {
    errorHandler(err, req, res, next, logger);
});

Using with a Custom Error Class

You can pass a custom error to the error handler. The error must be an instance of the CustomError class. In the example below, we are using a custom error package. You can create your own custom error, or just pass in a generic error such as the built in Error class.

const { CustomError } = require('@josephdaw/error');

app.all('*', (req, res, next) => {
    const err = new CustomError('Route Not Found', 404);
    next(err);
});

Handling Async Errors

You can use the error handler to handle async errors. In the example below, we are using the asyncErrorHandler package to wrap our async route handlers. This will throw the error back to our global error handler.

const { asyncErrorHandler } = require('@josephdaw/error-handler');

app.get('/async', asyncErrorHandler(async (req, res, next) => {
    const data = await getData();
    res.json(data);
}));

Issues and Requests

Please report any bugs or feature requests via GitHub Issues.

Security

Please report any security issues to [email protected]. Find more information in our Security Policy

Contributing

All development of this project happens through GitHub. We welcome constructive collaboration from the community to help implement new features or fix bugs. For more information please read our Contribution Guide

Changelog

Every significant change is documented in the changelog file.

License

This project is released under the MIT License.