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

@digibear/middleware

v1.0.1

Published

A Middleware pipeline written with Typescript.

Downloads

17

Readme

@digibear/middleware

This is a middleware engine written in typescript that I've used on a couple of projects now. I've decided to turn it into it's own module for future reuse.

Installation

yarn add @udigibear/middleware

Usage

When you call the pipline function and assign it to a variable, you are able to pass a coma seperated list of middleware functions to add to the middleware queue.

import { pipeline } from "@digibear/middleware";

interface Context {
    [key: string]: any
}

const engine = pipeline<Context>((ctx, next) => {
    ctx.foobar="baz";
    next();
})

Not all middleware has to be added when the factory function is first invoked. Instead, you can assign middldeware to the system later with the use method.

engine.use(async (ctx, next) => {
  await new promise(res => setTimeout(() = res, 2000));
  ctx.another = 123;
  next();
});

Then when we're ready to run the middleware engine, we'll create it's it's initial context, and then pass that context to the engine for processing.

(async () => {
  const context: Context = {};
  await engine.exec(context);
  console.log(context);
})();

// => { foobar: "baz", another: 123 }

Errors

If an error happens in your middleware pipeline, you can assign an error handling middleware at the end of the queue.


engine.use((ctx, next) => {
  fs.readFile(ctx.path, {}, (err, file) => {
    if(err) next(err)
    
    // .. Do something
    
    next();
  })
})


// .. More middleware ...

engine.use((cyx, next, error) => {
 if (error) console.error(error.message);
})

Development

yarn -Dev install

Testing

yarn test

License

MIT