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 🙏

© 2026 – Pkg Stats / Ryan Hefner

http-codes

v2.1.0

Published

Map of HTTP status messages to codes based on Node's built-in (inverse) map

Readme

http-codes

Map of HTTP status messages to codes — the inverse of Node's built-in STATUS_CODES.

Stays in sync with Node: when the runtime adds or renames a status, this package picks it up automatically.

NPM

npm install http-codes
import codes from 'http-codes'
// or
const codes = require('http-codes')

codes.OK          // 200
codes.NOT_FOUND   // 404
codes.IM_A_TEAPOT // 418

Why use this

  • Ultra simple — one small module, zero dependencies
  • Always current — derived from Node's built-in map at load time
  • TypeScript types included

API

The module exports a plain object. Each key is the status message in SCREAMING_SNAKE_CASE; each value is the numeric code.

import codes from 'http-codes'

if (res.statusCode === codes.NOT_FOUND) {
  // …
}

Keys are normalized from Node's messages: apostrophes removed, hyphens and spaces become underscores, then uppercased ("Request Timeout"REQUEST_TIMEOUT).

The exact set of keys depends on your Node version. Run npm test to print the current map.


Upgrading from 1.x

No code changes needed if you used require('http-codes') and property access — that is the entire 1.0.0 API and it is preserved in 2.0.0.

2.0.0 is a major release because of packaging (TypeScript, dist/, dual ESM/CJS, built-in types, tooling) and the long gap since 1.0.0 — not because the require() shape changed.

Full compatibility matrix, dependent-audit commands, and smoke tests: docs/backwards-compatibility.md.


License

MIT — see LICENSE.