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

kopi-error-handler

v1.0.4

Published

This library is used to save time for reimplementing express not found and error handler, along with a nice and pretty method to return an error response with a proper error structure.

Downloads

4

Readme

Kopi Error Handler

This library is used to save time for reimplementing express not found and error handler, along with a nice and pretty method to return an error response with a proper error structure.

Installation

Using npm: npm install --save kopi-error-handler

Usage (express)

const KopiErrorHandler = require('kopi-error-handler');

const app = express();
app.use((req, res, next) => KopiErrorHandler.handleNotFound(req, res, next));
app.use((error, req, res, next) => KopiErrorHandler.handleError(error, req, res, next));

Usage (create a custom error)

const KopiErrorHandler = require('kopi-error-handler');

const error = KopiErrorHandler.create({
  code: 404,
  status: 'Not Found',
  message: 'custom message',
  data: { someKey: 'some value' },
  stackTrace: true,
});
throw error;

Configurations

code: (integer, optional, default: 500) HTTP status code.

status: (string, optional, default: mapped from code) Message text, used if no message.

message: (string, optional) Error message text, overwriting message from JavaScript Error object.

data: (error/object, optional) main body of error.

stackTrace: (boolean, optional, default: false) Flag to include stacktrace.

Environment Variables

ERROR_HANDLER_LOG_NOT_FOUND_ROUTE: (boolean, optional, default: false) Logs not found route

ERROR_HANDLER_LOG_ERROR: (boolean, optional, default: false) Logs errors before responding