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

express-middlewrap

v1.0.0

Published

Turn any function, including async, into express middleware, and use any express middleware as a function.

Readme

Express Middlewrap

Why?

Express middlewares pass errors to a callback. Javascript already has two error flows with synchronous and asynchronous code.

Express middlewares call a callback (sometimes more than once...) instead of returning. Javascript already has two standard return flows with synchronous and asynchronous code.

This wrapper converts synchronous and asynchronous flows to express-style callback flows when passed a callback, and converts callback style flows to the underlying synchronous or asynchronous function when not passed a callback.

Examples

Wrapped functions no longer require calling next or catching error to next function. Next will be called when the function completes or the promise returns or a catchable error is thrown.

Automatically calls next on function return or promise completion.

const mw = require('express-middlewrap');

app.get("/:userId/:docId", [
    mw((req) => {
        // Any errors thrown are called with next.
        checkUserAuth(req.params.userId, req.headers.authorization);
        // Next called implicitly.
    })
    // Simple, straight forward use of async/await.
    mw(async (req, res) => {
        // Any errors thrown are called with next.
        await checkUserOwnsDoc(req.params.userId, req.params.docId);
        // Next called implicitly.
    }),
    (req, res, next) => {
        const docStream = getDocStream(req.params.docId);
        docStream.pipe(res);
        docStream.on("error", (e) => next(e));
        docStream.on("end", () => next());
    }
]);

Limitations

Uncaught Exceptions

Doesn't work properly with middleware that calls next asynchronously and without returing a promise, i.e. setTimeout, event handlers. Promisify them first.

Won't work properly.

mw((req, res, next) => {
    setTimeout(next, 500);
})

mw((req, res, next) => {
    new Promise(() => { /* ... */ }).then(next);
})

Can work properly.

mw((req, res, next) => {
    return new Promise((resolve) => setTimeout(resolve, 500)).then(next);
})
mw((req, res, next) => {
    return new Promise(() => { /* ... */ }).then(next);
})

Doesn't wrap everything in promises.

We don't want to promise what we can already deliver.

Sync code stays sync.

mw((req, res, next) => { return "bar"; }})() // => "bar"