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

counter

v0.1.1

Published

A counter for use with asynchronous operations in Node.

Downloads

3,166

Readme

counter

A counter for Node, installed with npm install counter. Watches changes to its value and emits an event when it hits a target, and comes in handy when you're waiting on a large number of asynchronous operations but want a smaller callback queue in memory compared to using a control flow library or similar tool.

Usage

In the example below, we create a counter and then loop over a number of files. The counter counts up for every file in the loop, and counts down when that file is loaded. Before the async calls are complete, we listen for the "target" event then start the counter. Once it hits zero again

var counter = require('counter'),
    count = counter(0);

files.each(function(err) {
    count.value += 1; 
    fs.readFile(function(err, value) {
        count.value -= 1;
    });
});

count.once('target', function() {
    console.log('We have read every file now');
}).start();

By default the counter's target is zero, but you can change this with the target option. Additionally, you can disable the counter after it's first triggered with the once option.

var counter = require('counter'),
    count = counter(0, { target: 5, once: true }),
    i, l = 5;

count.on('target', function() {
    console.log('This is only called once');
}).start();

for (i = 0; i < l; i += 1) {
    count.value += 1;
}

count.value = 5;

If you didn't include the once option above, the counter would trigger twice.