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

exec-stack

v1.1.0

Published

```javascript $ npm install exec-stack ```

Downloads

2

Readme

ExecStack npm version

Installation

$ npm install exec-stack

Example

const ExecStack = require('exec-stack');
const stack = new ExecStack();

stack.use('cars', next => {
	console.log('I\'m specifically interested in cars');
	next();
});

stack.use((event, next) => {
	console.log('I\'m generic. Hence interested in anything, also', event);
	next();
});

stack.run('cars');
stack.run('bikes').then(console.log('Done!'));

Output:

I'm specifically interested in cars
I'm generic. Hence interested in anything, also cars
I'm generic. Hence interested in anything, also bikes
Done!

Methods

Optional arguments are written in cursive.

.use(event, callback)

Push a middleware to the stack. If event is omitted, the callback will be called for every execution of the stack.
Returns the position of the middleware in the stack.

.unuse(position)

Removes a specified middleware from the stack. The middleware is being referenced by a number representing its position in the stack.

.run(event, ...args)

Any other argument that is given to .execute() will also be passed to the functions in the stack.
Returns a promise that is being resolved after everything has finished.
If any middleware calls next.throw() the promise will be rejected.

.context(context)

Set the context to be applied to middleware. When context is omitted it will be cleared to an empty object.

Breaking the loop

If you want to stop the execution of the stack use next.throw(*error*) which also will reject the promise returned by .run()