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

countn

v3.0.0

Published

Simple control flow, for counting callbacks

Downloads

9

Readme

countn

countn is a simple control flow for counting callbacks.

Build Status

Installation

$ npm install countn

Basic Example

Here is a example of simple async scheduling. Where we have subscribed to execute some code after all concurent tasks have finished.

var cb = countn(5, function(err, results) {
  console.log('results: ', results)
})

cb(null, 'this is example call')
setTimeout(function() {
  cb(null, 'this is last call')
}, 500)
setTimeout(cb, 100)
setTimeout(cb, 200)
setTimeout(cb, 400)

Example with error call

Here is a example when error occured

var cb2 = countn(3, function(err) {
  console.log('example exited with error: ' + err)
})

cb2(null, 'this is first ok call')
setTimeout(function() {
  cb2('this is first error call')
}, 100)
setTimeout(function() {
  cb2(null, 'this is second ok call')
}, 200)

What's it good for?

countn is not ment to replace any control flow library, rather as i am still counting callbacks, i just wanted a simple library for a little suggar on top of it.

And i believe its much readable having everything in same hierarchy instead of complex nesting structures.

Running tests

$ npm install
$ npm test

Authors

License

MIT