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

holdon

v0.2.1

Published

A simple, non atomic, unique key/values based cache

Downloads

164

Readme

holdon

build status

A simple, non atomic, unique key/values based cache

Specially handy in all those situations where one unique id can perform an asynchronous action you don't want to drop the first time is called but you want to store all listeners waiting for such result.

Simplified API for common cases

module.exports = function (path, callback) {
  // true only if created first time
  if (cache.add(path, callback)) {
    fs.readFile(path, function (err, res) {
      // remove returns the object too
      cache.remove(path).callback.forEach(
        onFileRead, {err: err, res: res}
      );
    });
  }
};

function onFileRead(callback) {
  callback.call(null, this.err, this.res);
}

Full API example

// module: filereader
var fs = require('fs');

// a generic module cache
// with a callback property
var cache = require('holdon').create(['callback']);

function onFileRead(callback) {
  callback.call(null, this.err, this.res);
}

module.exports = function (path, callback) {
  if (!cache.has(path)) {
    fs.readFile(path, function (err, res) {
      var result = cache.get(path);
      // clean this id
      cache.remove(path);
      // invoke all waiting callbacks
      result.callback.forEach(onFileRead, {err: err, res: res});
    });
  }
  // add the path to the queue
  cache.add(path, callback);
};

In another file ...

var filereader = require('filereader');

// whenever is needed
filereader('anyFile.md', function (err, res) {
  // do something ...
});

filereader('anyFile.md', function (err, res) {
  // do something ...
});

filereader('anyFile.md', function (err, res) {
  // do something ...
});

// it does not matter how many asking, the disk will read it once