npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




A lightweight wrapper for Express 4's Router that allows middleware to return promises





npm version

A simple wrapper for Express 4's Router that allows middleware to return promises. This package makes it simpler to write route handlers for Express when dealing with promises by reducing duplicate code.

Getting Started

Install the module with npm

npm install express-promise-router --save

or yarn.

yarn add express-promise-router

express-promise-router is a drop-in replacement for Express 4's Router.


Middleware and route handlers can simply return a promise. If the promise is rejected, express-promise-router will call next with the reason. This functionality removes the need to explicitly define a rejection handler.

// With Express 4's router
var router = require("express").Router();

router.use("/url", function (req, res, next) {

// With express-promise-router
var router = require("express-promise-router")();

router.use("/url", function (req, res) {
  return Promise.reject();

Calling next() and next("route") is supported by resolving a promise with either "next" or "route". No action is taken if the promise is resolved with any other value.

router.use("/url", function (req, res) {
  // equivalent to calling next()
  return Promise.resolve("next");

router.use("/url", function (req, res) {
  // equivalent to calling next('route')
  return Promise.resolve("route");

This package still allows calling next directly.

router = require("express-promise-router")();

// still works as expected
router.use("/url", function (req, res, next) {

ES6 Imports

express-promise-router can be imported via ES6 imports. The Router constructor is the default export.

import Router from "express-promise-router";
const router = Router();

Async / Await

Using async / await can dramatically improve code readability.

router.get('/url', async (req, res) {
    const user = await User.fetch(;

    if (user.permission !== "ADMIN") {
      throw new Error("You must be an admin to view this page.");

    res.send(`Hi ${}!`);

Error handling

Just like with regular express.Router you can define custom error handlers.

router.use((err, req, res, next) => {

Frequently Asked Questions

Cannot read property '0' of undefined

This error may indicate that you call a method that needs a path, without one. Calling router.get (or post, all or any other verb) without a path is not valid. You should always specify a path like this:

// DO:
router.get("/", function (req, res) {

// DON'T:
router.get(function (req, res) {

For more information take a look at this comment.

Can i use this on app?

We currently don't support promisifying the app object. To use promises with the top-level router we recommend mounting a Router on the app object, like this:

import express from "express";
import Router from "express-promise-router";

const app = express();
const router = Router();

router.get("/", function (req, res) {

Why aren't promise values sent to the client

We don't send values at the end of the promise chain to the client, because this could easily lead to the unintended leak of secrets or internal state. If you intend to send the result of your chain as JSON, please add an explicit .then(data => res.send(data)) to the end of your chain or send it in the last promise handler.


Add unit tests for any new or changed functionality. Lint and test your code using npm test.

Unit tests use mocha and chai.

We use eslint, but styling is controlled mostly by prettier which reformats your code before you commit. You can manually trigger a reformat using npm run-script format.

Release History



Licensed under the MIT license.

Initial implementation by Alex Whitney
Maintained by Moritz Mahringer
Contributed to by awesome people