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

koa-7xx-statuses

v1.0.6

Published

A tiny library to add 'RFC 7xx: Develop Errors' status codes and messages which also retains the functionality to add other custom statuses

Downloads

11

Readme

Koa 7xx Statuses

NPM version node version npm download

Are your koajs REST APIs just not ‘expressive’ enough? Do you spend your days wishing you could be truly transparent in how you represent failed HTTP calls to your consumers? Well, now you can! With koa-7xx-statuses!

Leverage some of those good old standbys such as:

  • 735: Fucking IE
  • 745: I don’t always test my code, but when I do, I do it in production
  • 747: Motherfucking Snakes on the Motherfucking Plane!
  • 799: The End of the World

…and many, many more!

(Full list can be found @ RFC for the 7XX Range of HTTP Status codes - Developer Errors)

The module definition is extremely simple. Just mount the module onto the app using koa-mount and provide additional codes as a JSON object if you wish.

Most credit goes to Srinivas Iyer who originally wrote the fantastic package called koa-custom-statuses which i simply improved upon. Thank you Srini!


const Koa = require('koa');
const mount = require('koa-mount');
const k7xxStatuses = require('koa-7xx-statuses');
const app = new Koa()

const developerStatusCodes = new k7xxStatuses();
app.use(mount(developerStatusCodes));

app.use(async (ctx, next) => {
        await next();
        ctx.status = 799;
});

Of course, if you wish to overwrite, or add your own status codes, just provide them as an argument:

const Koa = require('koa');
const mount = require('koa-mount');
const k7xxStatuses = require('koa-7xx-statuses');
const app = new Koa()

// Cause you feel like it
optionalCodes = {
                    '200': 'Im Loving it!!',
                    '499': 'Cos I can come that close to 500',
                    '999': 'Polish Programmer'
                };

const developerStatusCodes = new k7xxStatuses(optionalCodes);

There are just some basics you need to keep in mind for OPTIONALLY ADDED codes:

  • The status codes can be 3 digit numbers only.
  • The codes you declare will overwrite the Koa Defaults.
  • You can only use default Koa codes or the codes defined in the module. Any others will throw an error

License

MIT