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

myddle

v0.5.0

Published

Context carrying Middleware for regular functions, with error handlers.

Readme

                  .___  .___.__          
  _____ ___.__. __| _/__| _/|  |   ____  
 /     <   |  |/ __ |/ __ | |  | _/ __ \ 
|  Y Y  \___  / /_/ / /_/ | |  |_\  ___/ 
|__|_|  / ____\____ \____ | |____/\___  >
      \/\/         \/    \/           \/ 

Context carrying Middleware for regular functions, with error handlers. Kinda like Connect/Express middleware but without the HTTP request/resonse. Or thinking about it another way, like async#applyEachSeries but with error functions.

Build Status

Synopsis

var myddle = require('myddle');

myddle({}, [ fn1, fn2, ...], function(err) {
    // called when all functions have been called
});

Each middleware function has the signature:

function fn1(context, done) {
    // ... do something and store result in context
    return done();
}

And every single function will receive the context when called.

You can pass a context to start off with, or it will default to {}:

// equivalent
myddle({}, [ fn1, fn2, ...], function(err, context) {
    // ...
});

// same as above
myddle([ fn1, fn2, ...], function(err, context) {
    // ...
});

In all cases, the final function is called in the standard Node.js way, with err as the first argument. Whether err is set or not, the current context is always passed as the second argument.

Errors

If done() is called with an error, then the regular middleware functions are skipped over and any error handler middlewares are called with the error. Each error handler middleware has the following signature:

function fn1(err, context, done) {
    // ... do something and store result in context

    // to propagate the error (or send a new one), call done with it
    return done(err);

    // or

    // to cancel the error call done without any error
    return done();
}

Author

Written by Andrew Chilton - Blog - Twitter.

License

(Ends)