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

batches

v0.1.0

Published

Control concurrency of massive async loops

Downloads

10

Readme

batches

You have to make thousands of database queries or API calls? You don't want to throw those millions of queries all at once at your poor backend? Batches is here to help you out.

Examples

For one example is worth a thousand words:

var b = require('batches').batch({ concurrent: 10, context: 'Jimmy', collectData: true });
for (var i = 0; i < 100; ++i) {
	b.add(function(next, idx) {
		setTimeout(function() {
			console.log('This is call #' + (idx + 1) + ', ' + this);
			next(null, 'Result #' + (idx + 1));
		}, 101-idx);
	});
}
b.when(function(errors, data) {
	console.log('All done.');
	console.log(data);
});

API

batches.batch(options)

Create a new batch. Available options:

  • concurrent: How many jobs to run at the same time. Default: 100
  • context: Context to call the job-functions in. Default: the batch-object itself
  • exitOnError: If true, no new jobs are started after the first error occurred. Default: true
  • collectData: If true, the data passed to next-callbacks is collected and passed to the when-callback when all jobs are finished. Default: false

batch.add(callback)

Add a new job to a batch. The callback gets called immediately if concurrency allows it. The arguments of the callback are:

  • next: Has to be called when the job is done. Can be passed an error object and data.
  • index: The index of the job (the jobs get called in the order they are added to the batch)

batch.when(callback)

Add a callback that gets called when all jobs have finished (or exitOnError is set to true and an error occurred). First argument is either null or an array of errors (where array indices and job-index match up), the second argument is either an empty array (when collectData is set to false) or an array containing all data passed to the next-callbacks, again with indices matching the index-parameter of the jobs.