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

pretty-response

v1.0.1

Published

Express middleware that exposes functions to work with HTTP status codes

Downloads

6

Readme

Pretty Response

Build Status Coverage Status Code Climate npm version

Express middleware that exposes functions to work with HTTP status codes

Pretty Response exposes all HTTP codes as functions on response as a middleware. So you can plug it wherever you want to and have a more expressive code than using standard response.status(CODE).

Install

$ npm install --save-dev pretty-response

Usage

var express = require('express')
var pretty = require('pretty-response')

var app = express()
	.use(pretty)

Or you can use specifically on the routes you want to.

Then you can use descriptive names as functions to create RFC 2616 specific response:

app
.get('/', function (req, res, next) {
	res.ok().send()
})

All functions are using camel-cased names. For instance notFound, internalServerError and created. It's easier if you take a look at the the codes file.

License

MIT