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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@atz3n/express-utils

v1.4.3

Published

A utilities library for express servers

Readme

express-utils

A utilities library for express servers

Installation

npm install @atz3n/express-utils

you also have to have body-parser, express-async-errors and express-validator installed.

npm install body-parser express-async-errors express-validator

Add the errorHandler function after your routes. Have a look into the test server for an example.

Content

The library contains the following throwable errors:

BadRequestError     : returns status code 400
NotAuthorizedError  : returns status code 401
NotFoundError       : returns status code 404
InternalError       : returns status code 500

It also contains the following middleware functions:

validationRequest   : validates express-validator validation results
validateAuthToken   : validates an auth token
validateOrigin      : validates the origin
errorHandler        : sends error responses to the client

Have a look into the test server for example usage.

Development

To initialize the project just clone this repository and run

npm install

For linting run

npm run lint

You can try to autofix lint errors with

npm run lint:fix

For unit tests run

npm test