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

node-interactor

v0.0.3

Published

Interactor/organizer pattern for node/javascript

Downloads

10

Readme

Interactor

Interactor/organizer pattern for node/javascript.

Basic Usage

An interactor is an object that manipulates a 'Context' (really, just a hash) during a 'perform' method.

Here is a basic interactor:

var perform;
perform = require('node-interactor');

function Interactor() {}
Interactor.perform = perform;
Interactor.prototype.perform = function() {
  console.log(this.context.input);
}

Interactor.perform({ input: 'Hello, World!' });
// Hello World!

Seem like a lot of work for little reward? That's where Organizers come in:

Organizer = {};
Organizer.perform = perform;
Organizer.organize = [ Interactor1, Interactor2 ]

Organize.perform();
// Performs Interactor1 and Interactor2

Contexts

When you perform an interactor or an organizer, you will almost definitely pass in a hash. The perform function turns this into a special Context object, which is shared across all interactors and organizers performed by the initiating organizer.

function FirstInteractor() {}
FirstInteractor.perform = perform;
FirstInteractor.prototype.perform = function() {
  this.context.sum = this.context.num * 2;
}

function SecondInteractor() {}
SecondInteractor.perform = perform;
SecondInteractor.prototype.perform = function() {
  console.log('The sum is ' + this.context.sum);
}

Organizer = {};
Organizer.perform = perform;
Organizer.organize = [ FirstInteractor, SecondInteractor ];

result = Organizer.perform({ num: 1 });
// "The sum is 2"
console.log(result.sum);
// 2

Fail, succeed, skip

At any point during an interactor's perform method, you may call this.fail, this.succeed and this.skip to halt the current interactor.

Succeed and fail also update the context's status to 'failed' and 'succeeded', respectively.

While performing an organizer, if the context's status change to failed or succeeded, the organizer will not perform any remaining interactors. However, skipping an interactor does not halt the organizer, and any remaining interactors will be performed.

Additionally, succeed and fail may be passed a message, which is added as the message property of the context.

Here is a failure example:

function FirstInteractor() {}
FirstInteractor.perform = perform;
FirstInteractor.prototype.perform = function() {
  this.fail('my message');
}

function SecondInteractor() {}
SecondInteractor.perform = perform;
SecondInteractor.prototype.perform = function() {
  console.log('This never gets logged');
}

Organizer = {};
Organizer.perform = perform;
Organizer.organize = [ FirstInteractor, SecondInteractor ];

result = Organizer.perform();
console.log(result.status);
// "failed"
console.log(result.message);
// 2