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

status-range-handler

v1.0.1

Published

Allows a user to handle error responses easily and quickly by categorizing standard responses by range

Downloads

40

Readme

status-range-handler

This module allows a user to handle error responses easily and quickly by categorizing standard responses by range.

installation

npm install status-range-handler

the HandlerObject

HandlerObject = <args extends any[]> (res: Response, ...args) => boolean
HandlerObject = <args extends {[key: string]: any}>(res: Response, args) => boolean

This is important to the functionality of the module. There are several options to how you can set your status selectors. The following are examples of those styles and their behaviors:
207- responses with exact status 207 will run this function
300-404 responses with any status from 300 to 404 will run this function
40# responses with any status matching 40[0-9] will run this function
4## responses with any status matching 4[00-99] will run this function
400+ any response with a status greater than 400 will run this function
400- any response with a status less than 400 will run this function

Note that this is the priority order. Only the first matching handler will be run.

functions

init(HandlerObject)

This will generate your application defaults. When this is set, calling the core statusRangeHandler will use these as a fallback if the response status doesn't match any of those provided in its HandlerObject.

statusRangeHandler(res: Response, handlers?: HandlerObject, ...args)

(args are then passed into the resulting handler in order)

statusRangeHandler(res: Response, {handlers?: HandlerObject, ...args})

(args are then passed into the resulting handler as an object)

statusRangeHandler(res: Response, ...args)

(args are then passed into the resulting hander in order)

This is the core function. It allows you to wrap the response object, combined with a HandlerObject, and runs the functionality with the provided HandlerObject. If the response status matches none of the handler keys, it will then fall back to the default global handlers. If it is also not matched in the global handlers, no handling will occur, so make sure you're accounting for that.