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

callback-collector

v1.0.0

Published

An async utility to collect callbacks and then execute another when all have been called

Downloads

3

Readme

callback-collector

When I was first getting acquainted with node.js, I was experimenting with different ideas for handling async callbacks. This is one of the ideas I had where you wrap each of your callbacks in a call to callback-collector. callback-collector intercepts each callback and counts the number of still pending callbacks.

Ultimately it is not what I settled on for general use; I do not recall exactly why. But, here it is for good measure anyway.

install

npm install callback-collector

example

var request = require('request');
var cbc = require('callback-collector');

var c = cbc(function () {
	console.log('0. all callbacks have been called');
});

setTimeout(c(function () {
	console.log('1. setTimeout is done');
}), 1000);

request('https://www.google.com', c(function (err, res, data) {
	console.log('2. https request is finished');
}));

output:

2. https request is finished
1. setTimeout is done
0. all callbacks have been called

license

MIT