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 🙏

© 2024 – Pkg Stats / Ryan Hefner

execute-middleware

v1.0.3

Published

Execute arbitrarily complex middleware in the Express format.

Downloads

119

Readme

Use-case

This utility is for the execution of arbitrarily complex express-style middleware.

Express middleware is executed by allowing either a middleware function or an array, calling each piece of middleware and awaiting the callback next to be invoked. When next is invoked, the next middleware is called. If next is invoked with an argument, this is treated as an error. Upon being invoked with an error, all subsequent middleware is ignored until an error handler middleware is encountered, defined as a piece of middleware expecting 4 arguments, rather than 3.

This, for example, is how error handling middleware looks:

(err, req, res, next) => {
  // Error handler
}

As compared to normal middleware, which would be skipped over if an error is being propagated through the middleware:

(req, res, next) => {
  // Normal middlware
}

Note that the names of the arguments don't matter, just the amount of expected arguments.

Usage

$ npm install execute-middleware

const executeMW = require('execute-middleware');

// Some middleware
const SOME_MIDDLEWARE = [
  (req, res, next) => {
    console.log('hi.');
    next()
  },
  [
    (req, res, next) => {
      console.log('hey');
    },
    (err, req, res, next) => {
      console.log('I will not be called, because im not an error.');
    }
  ]
];

// Execute MW serially
executeMW.serial(SOME_MIDDLEWARE);

// Execute MW concurrently
executeMW.concurrent(SOME_MIDDLEWARE);