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

json-courier

v1.0.2

Published

simple APIs client

Readme

json-courier is a utility library for creating handling on the client for simple APIs.

Only the POST method and JSON format are supported. This limitation is intentional; this small library is designed to help with the boring parts not do everything.

Basic Example:

var courier = require('json-courier');
var api = courier('/api/1.0');

var ExampleRepo = function () {
	// the type's constructor
};

ExampleRepo.prototype = {

	// accepts is an array of status'es that should go though resolve,
	// everything thats not in accepts goes though reject path; errors also
	// go though reject path (you can check for "stack" prop to diferentiate)
	list: function (payload, accepts) {
		// a promise will be returned; the lie library is used under the hood
		return api.req('example/list', payload, accepts);
	},

	// same as above; shorthand syntax
	add: api.f('example/add')

};

module.exports = ExampleRepo;

On the server, all api requests come in the form of,

{
	"auth" : "[ value of api.auth() ]", 
	"data" : "[ the payload ]"
}

If you recieve null for auth the request should be treated as coming from a user that's not authenticated.

Authentication

You can set and retrieve auth via api.authWith(authToken) and api.auth()

See example above for how the request looks.

Server Response

The server is expected to respond with at least status and data. The data field should be null in case of no response.

Here is a the simplest success response:

{
	"status" : "success",
	"data"   : null
}

An error should have status set to error and set the error message in the data field.

Example error:

{
	"status" : "error",
	"data"   : "Example error"
}

You can have any status you wish. It's recomended you don't hardcode the accepts value when defining the API on the client side; it's better for the calling code to specify what status it's capable of accepting.

Domain

By default there is no domain, the path is assumed relative to the current root of the current domain. To set a domain use courier.domainPrefix; this is a global setting however.