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

eventcollector

v0.1.5

Published

Node/JavaScript library for collecting multiple events into a single one.

Downloads

3

Readme

eventcollector

Node/JavaScript library for collecting multiple events into a single one.

Sometimes one needs to wait for various events to be emitted before doing something else. There are many solutions for this subject but most of them require passing the event callbacks to that library/module. While this is good in certain cases it is not so nice when one wants to code events within a prototype method of a custom class in a OO fashion.

eventcollector provides a different approach in which the user just needs to invoke a library method within his callback definitions.

Install in Node

$ npm install eventcollector

Install with Bower

$ bower install eventcollector

Manual installation for Browser apps

Take the browserified file at build/eventcollector.bundle.js and include it in your HTML:

<script src='js/eventcollector.bundle.js'></script>

The browserified file exports the window.eventcollector function.

Usage

In Node

// We expect 2 events.
var ec = require('eventcollector')(2);

ec.on('done', function(fired, total, data) {
  console.log('event %d of %d emitted', fired, total);
  console.log('event description:', data);
});

ec.on('alldone', function(total) {
  console.log('all the required %d events have been emitted', total);
  // Continue your work here.
});

// Event #1.
process.nextTick(function() {
  // Notify the eventcollector.
  ec.done('event #1');
});

// Event #2.
setTimeout(function() {
  // Notify the eventcollector.
  ec.done('event #2');
}, 1000);

produces:

event 1 of 2 emitted
event description: event #1

... (1 second) ...

event 2 of 2 emitted
event description: event #2
all the required 2 events have been emitted

In the Browser

<script src='js/eventcollector.bundle.js'></script>

<script>
  var ec = window.eventcollector(2);

  ec.on('alldone', function(total) {
    // ...
  });
</script>

Documentation

Function eventcollector(total, timeout)

In Node:

var eventcollector = require('eventcollector');

var ec = eventcollector(total, timeout);

In the Browser:

var ec = window.eventcollector(total, timeout);

Returns an instance of EventCollector.

  • param {Number} total: Number of events expected.
  • param {Number} timeout (optional): Emit 'timeout' if the required events have not fired before this value (in ms).

Class EventCollector

The main class. It is an EventEmitter.

Method done(data)

Tell the EventCollector instance that an event has been emitted.

  • param {Object} data (optional): Custom data about the emitted event.

Method destroy()

Destroy the EventCollector instance. No more events will be emitted.

Event 'done'

Emitted for each fired event (this is, after each call to done()).

  • param {Number} fired: Number of fired events.
  • param {Number} total: Total number of required events to fire.
  • param {Object} data: The same custom data as provided in the done() method.

Event 'alldone'

Emitted when all the required events have fired.

  • param {Number} total: Total number of required events to fire.

Event 'timeout'

Emitted if the given timeout expires before all the required events have fired.

  • param {Number} fired: Number of fired events.
  • param {Number} total: Total number of required events to fire.

IMPORTANT: New 'done' events after the timeout will still be emitted unless the user calls destroy().

Release History

0.1.4 (2014-11-03)

  • Make test units work on Windows (use grunt-contrib-nodeunit).

0.1.3 (2014-10-24)

  • Remove 'error' event by ensuring done() is ignored once all the required events have been emitted.

0.1.2 (2014-10-23)

  • Complete documentation.

0.1.1 (2014-10-23)

  • Added a browserified file for using the library into Web applications.
  • Register eventcollector as a Bower package.

0.1.0 (2014-10-23)

  • First release.

License

Copyright (c) 2014 Iñaki Baz Castillo Licensed under the MIT license.