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

koa-map-router

v0.0.3

Published

a [too] simple router for koa

Readme

koa-map-router

A router for koa that's almost too simple.

Install

npm install --save koa-map-router

Usage

var app = require('koa')();
var Router = require('koa-map-router');

var router1 = new Router();
router1.get('/user', [loadUser, showUser]);
router1.put('/user', [loadUser, updateUser]);
router1.del('/user', [loadUser, deleteUser]);
app.use(router1.middleware());

var router2 = new Router();
router2.get('/hello/world', [function*() { this.body = ':)'; }]);
app.use(router2.middleware());

app.listen(3000);

How it works

For fast and simple lookup, routes are stored in a Map of path to a Map of method to a (composed) array of middleware generator functions.

The example in the "Usage" section creates these maps:

var router1 = {
  '/user': {
    'GET': [loadUser, showUser],
    'PUT': [loadUser, updateUser],
    'DELETE': [loadUser, deleteUser]
  }
};

var router2 = {
  '/hello/world': {
    'GET': [function*() { this.body = ':)'; }]
  }
};

The library offers a simple API on top of its underlying maps:

This:

router.get('/user', [loadUser, showUser]);

is sugar for:

router.addRoute('GET', '/user', [loadUser, showUser]);

which is sugar for:

router.routes.get('/user').set('GET', compose([loadUser, showUser]));

When a request comes in, it's pretty much matched like routes[this.path][this.method], though it's not exactly like that. For instance, an incoming HEAD request will match if you have a GET defined for the requested path.

What about wildcard, parameterized, globbing, or regexp routing?

This router does not support the sort of syntax you may be used to like:

router.get('/users/:id', ...)
router.get(/^users\/(\d+)$/, ...)

Instead, you could implement GET /users?id=1 (depend on query-params)

Or you can even pre-generate all of your routes:

var router = new Router();
var users = yield db.findAllUsers();
users.forEach(function(user) {
  router.get('/users/' + user.id, [loadUser, showUser]);
});

The tradeoff is that routing is constant time and the code is dead simple.