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

director.js

v1.2.0

Published

A command bus implementation for node.js

Downloads

185

Readme

Director.js License Build Status

Requirements

You will need node v6.0.0 or higher to be able to use director. Please get in touch or submit a PR if you need compatibility with lower versions or iojs.

Installation

yarn add director.js
//or
npm install --save director.js

Usage

Init

Director.js provides a simplistic bootstrap method as its default export.

const bus = require('director.js')();

bus.registry.register('command', handler);

bus.handle(command);

If you require more control over configuration you can build the bus yourself.

const director = require('director.js');

const bus = new director.Bus(registry, {
	locator, nameResolver, handlerResolver
});

bus.handle(command);
  • registry - can be anything as long as your locator can use it to retrieve a handle by command name, if your registry provides get(id) method, the default locator will work fine.
  • nameResolver(command) - given command, it will return its name - default locator will return command.ID property
  • locator(command, registry) - given command name returned by nameResolver, locator is responsible for returning a handler from registry - by default it will call registry.get(command)
  • handlerResolver(command, handler) - given command name and handler returned by locator it will return the command execution method, by default it will return handler['execute']

Registry

The memory registry is exported via director.MemoryRegistry and is the default registry used if no other is provided.

  • MemoryRegistry.register(name, handler) - register handler under name
  • MemoryRegistry.get(name) - return handler by name

Short example

(more complete example, with promises and callback based calls, can be found here https://github.com/michael-donat/director.js/blob/master/example.js)


const director = require('director.js');

class CommandHandler {
	execute(command) {
		console.log(command.param);
	}
}

class Command {
	constructor(param) {
		this.param = 1;
	}
}

Command.ID = 'command';

const bus = director();

bus.registry.register(Command.ID, new CommandHandler());

bus.handle(new Command('param'));

Contributing

All contributions are more than welcome. Fork and PR not forgetting about linting and testing.

License

MIT