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

co-control

v0.1.1

Published

start async jobs when you want, access the results when you want.

Downloads

8

Readme

Co-Control

Start async tasks when you want. Get them back as you want.

Reason

In standard co flow, yields dispatch async jobs and issue requests for the resulting data at the same time. This greatly limits your ability to control the async flow. Co-Control aims to solve this problem by providing a simple api that starts async jobs and later get the resulting data. Because only the get call needs to be yielded you are able to kick of complex routine flows with little work.

Here is a very simple perf suite to dispay why working the co-control way can make things faster for you.

node --harmony ./speed-run.js setTimeout

Install

npm install --save co-control

Example

var thunkify = require("thunkify");
var co = require("co");
var CoControl = require("co-control");

var slow = thunkify(function(cb){
	setTimeout(function(){cb(null, 20)}, 20);
});

var fast = thunkify(function(cb){
	setTimeout(function(){cb(null, 2)}, 2);
});

co(function*(cb){

	var controller = new CoControl();

	controller.start("sd", slow());
	controller.start("fd", fast());
	
	var fastData = yield controller.get("fd");

	// do some processing of fastData while we continue
	// to wait for slowData to do its thing

	var slowData = yield controller.get("sd");
});

API

start(key, yieldable)

Starts an async opperation and holds the result until you need it.

var thunkify = require("thunkify");
var yieldable = thunkify(function(cb){ setTimeout(function(){cb(null,20)}, 20);});
control.start("key", yieldable);

get(key)

  • key name of a start'd async opperation.

Returns the result of the async opperation. If the async opperation errored, it will throw that error.

var value = control.get("key");

all(keys)

  • keys an array of names of start'd async opperations.

Returns a key value map of the results of all the requested opperations. If any of the async opperations errored, it will throw that error.

var obj = control.all(["a", "b"]);

Results in...

{
	"a": "value",
	"b": "value"
}