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

fireplug

v1.0.2

Published

Simple engine for creating plugin-driven applications

Downloads

6

Readme

fireplug

Simple engine for creating plugin-driven applications

Usage

First, instantiate a plugin manager:

var PluginManager = require('fireplug');
var plugins = new PluginManager();

Next, start using plugins:

var pluginA = {
  method1: function(prev, param1, param2, cb) {
    cb(null, someValue);
  },
  method2: function(prev, param1) {
    return somePromise;
  }
};

var pluginB = {
  method2: function(prev, param1) {
    return prev;
  }
};

plugins.use(pluginA);
plugins.use(pluginB);
plugins.use(arrayOfPlugins);

A plugin is an object with methods. The methods each take, as their first parameter, the value (if any) from any previous plugin, additional parameters for the method, and a callback parameter. The plugin method can work synchronous by either:

  • Returning the previous result argument
  • Returning null
  • Returning a regular value
  • Throwing an error

...or asynchronously by:

  • Calling a node-style callback argument
  • Returning a promise

To invoke plugins, you call the method through the plugin manager in one of two ways, through invoke:

plugins
  .invoke('method1', arg1)
  .then(
    function(result) {
      // Handle result
    },
    function(err) {
      // Handle error
    });

...or, if you know a method is defined at least one plugin, you can use the method name directly:

plugins
  .method1(arg1)
  .then(
    function(result) {
      // Handle result
    },
    function(err) {
      // Handle error
    });

In either case, the plugins are invoked asynchronously so that the plugin author always have an asynchronous option. fireplug uses Promises/A+.

The suggested strategy for structuring a plugin-based application is to integrate a built-in set of plugins, then enable a consumer of your application to inject additional plugins.