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

gatherer

v0.0.1

Published

Fire a callback when a whole bunch of other callbacks are complete

Downloads

9

Readme

#Gatherer

Intro

When developing Node.js applications sometimes you need to know when a whole bunch of callbacks have finished. You could just use synchronous methods, but that defeats the point of using Node, doesn't it?

Gatherer lets you set a callback to be run after a whole bunch of other callbacks have returned, but because that sounds incredibly boring it uses a metaphor of parties:

Invite your guests to your gathering. Once all your guests have accepted their invites, start the party!

The Code

To install

npm install gatherer
cd node_modules/gatherer
npm install

In your javascript file.

var gathering = require('gatherer');

Creating a party

Create a new gathering..

var gathering = gatherer(); 

Create your invitations...

_.each(files, function( file ){
	gathering.createInvitation( function( accept, decline ){
		fs.readFile( file, 'utf8', function( err, data ){
			if( !err ){
				// do something with your file data..
				accept();
			} else {
				decline();
			}
		});
	});
	
});

Send the invitations, executing a callback when they're done. Returns 'err' if there's an err, otherwise nothing.

gathering.sendInvitations(function(err){
	if(!err){
		// all invites were accepted
	} else {
		// some invites were declined... err === number of declines
	}
});

You can also set a limit on how long you want to wait for the invites:

gathering.sendInvitations(function(){
	if(err==='Error: Timed out'){
		// it waited 2000 miliseconds then gave up			
	}
}, { timeout : 2000 }) // will give up after 2000 ms. Warning: This doesn't cancel the execution of callbacks that are still running.

Run the tests

You need mocha and should.js.

make test