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

refcount

v0.1.2

Published

count things on an observable stack

Downloads

236

Readme

refcount

count things on an observable stack

installation

$ npm install refcount

usage

let's say you're streaming some things

stream.on('data', function (x) {
  // do stuff async with x
})

and you want to add a final step after all the async stuff is done. With refcount, we can keep track of how many requests we've sent off and be notified when they've all been handled:

var refcount = require('refcount')

var counter = refcount()

stream.on('data', function (x) {
  counter.push()
  doStuff(x, function () {
    counter.pop()
  })
})

counter.on('clear', function () {
  console.log('we\'re all done here!')
})

We can check the current counter number like so:

counter.i

It also keeps track of the high water mark, that is, the highest value the counter ever reached:

var counter = refcount(20)
counter.pop(15)

counter.i
// => 5

counter.highwater
// => 20

We can also listen for push and pop events using the standard EventEmitter interface:

counter.on('push', function () {
  console.log('add one')
})

counter.on('pop', function () {
  console.log('subtract one')
})

For memory purposes, consider using .once:

counter.once('clear', function () {
  console.log('done')
})

api

refcount(), refcount(initial : Number)

Initializes a new refcounter. If an initial count is not specified, it defaults to 0.

refcount#push(), refcount#push(delta : Number)

Increments the count by 1 or delta. Returns the current counter value.

refcount#pop(), refcount#pop(delta : Number)

Decrements the count by 1 or delta, to a minimum of 0. Returns the current counter value.

refcount#i : Number

The current counter value

refcount#highwater : Number

The highest counter value

events

clear: no arguments

Fires when a .pop operations results in the counter getting down to zero.

push: delta : Number, totalCount : Number

Fires after a push event. delta is the number added to the total count, and totalCount is the new total after the push operation.

pop: delta : Number, totalCount : Number

Fires after a pop event. delta is the number subtracted from the total count, and totalCount is the new total after the pop operation.

running the tests

$ npm test

contributors

jden [email protected]

license

MIT. (c) 2013 Agile Diagnosis [email protected]. See LICENSE.md