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

meet

v2.0.0

Published

Provides a way to start multiple tasks with a single callback when all are finished

Downloads

29

Readme

Meet

Provides a way to start multiple tasks with a single callback when all are finished.

Install

npm install meet

Run tasks cuncurrently

var Meet = require("meet")
var meet = new Meet()

meet.start( function() {
	var done = this
	// do stuff
	done()
})

meet.start( function() {
	var done = this
	// do other stuff
	done()
})

meet.allDone( function() {
	// all tasks have completed
})

Run tasks sequentially

meet.queue( function() {
	var done = this
	// do something first 
	done()
})

meet.queue( function() {
	var done = this
	// do something after the first thing 
	done()
})

meet.allDone( function() {
	// all tasks have completed
})

Example

var Meet = require("meet")
var meet = new Meet()

// These tasks are "started". They run concurrently & finish in random order
function timeTask(t, id) {
	var done = this
	setTimeout(function() {
		console.log("time "+id+": "+t)
		done()
	}, t)
}
meet.start(timeTask, Math.random() * 6000, "a")
meet.start(timeTask, Math.random() * 6000, "b")
meet.start(timeTask, Math.random() * 6000, "c")
meet.start(timeTask, Math.random() * 6000, "d")

// These tasks are "queued".  They run sequentially in the order that they were queued
function queueTask(t, id) {
	var done = this
	setTimeout(function() {
		console.log("queue "+id+": "+t)
		done()
	}, t)
}
meet.queue(queueTask, Math.random() * 2000, "A")
meet.queue(queueTask, Math.random() * 2000, "B")
meet.queue(queueTask, Math.random() * 2000, "C")
meet.queue(queueTask, Math.random() * 2000, "D")

// Note that the entire series of sequential tasks operates like a single concurrent
// task relative to the other concurrent tasks.

function finished(msg) {
	console.log(msg)
}

setTimeout(function() {
	console.log('seems like a nice time to set the completion call-back');
	meet.allDone(finished, "Everyone is done!")
}, 4000);