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

expressumer

v1.0.16

Published

**Expressumer** is a custom error handling middleware for Express.js applications, designed to handle errors gracefully and provide meaningful error messages in your API responses.

Downloads

5

Readme

ExpressUmer Documentation

About

Expressumer is a custom error handling middleware for Express.js applications, designed to handle errors gracefully and provide meaningful error messages in your API responses.

Getting Started

Install expressumer as an npm module :

npm install expressumer

Usage Instructions

Set Up Your Express Application:

In your Express application, you need to import Expressumer and set it up as middleware. Here’s a basic example:

const express = require('express');
const { errorHandler, ErrorResponse, ValidationError, NotFoundError } = require('expressumer');
const app = express();
// Sample route that throws a custom error
app.get('/custom-error', (req, res, next) => {
  return next(new ErrorResponse('This is a custom error message', 400));
});
// Sample route that throws a validation error
app.get('/validation-error', (req, res, next) => {
  return next(new ValidationError('Validation error occurred'));
});
// Sample route that throws a not found error
app.get('/not-found', (req, res, next) => {
  return next(new NotFoundError('Resource not found'));
});
// Use the custom error handler
app.use(errorHandler);
const PORT = process.env.PORT || 5000;
app.listen(PORT, () => console.log(`Server running on port ${PORT}`));

API Reference

ErrorResponse

new ErrorResponse(message: string, statusCode: number)

message : A descriptive error message . statusCode : HTTP status code (e.g., 400 for Bad Request).

Example

const { ErrorResponse } = require('expressumer');
throw new ErrorResponse('Invalid input data', 400);

ValidationError

new ValidationError(message: string)

message : A descriptive validation error message.

Example

const { ValidationError } = require('expressumer');
throw new ValidationError('Validation failed');

NotFoundError

new NotFoundError(message: string)

message : A descriptive message indicating that a resource was not found.

Example

const { NotFoundError } = require('expressumer');
throw new NotFoundError('The requested resource does not exist');

errorHandler

app.use(errorHandler);

errorHandler : Middleware function to handle errors thrown in the application. It should be added at the end of your middleware stack, after all routes.