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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ahead

v0.0.1

Published

An experiment with promises

Readme

Ahead

An experiment with promises

Some examples

@see example/example.js

var ahead = require('ahead');

Ahead provides a easy way to create promises. And lets you write asynchronous stuff that looks synchronous. Its thought as an experiment and not for real use. Error handling can get pretty confusing.

It adds two arguments to a function.

  • kept to keep the promise
  • broken to break the promise
var random = ahead(function (delay, kept, broken) {
    setTimeout(function () {
        kept(Math.random());
    }, delay);
});

var r = random(10);  // creates a promise for a random number
r.then(function (number) { console.log(number);});

Functions created with ahead can take promises as arguments the execution gets deferred until all promised arguments are resolved

var multiply = ahead(function (a, b, keep) {
    keep(a * b);
});

multiply(random(10), 3); // just looks synchronous

Ahead.shift converts a synchronous function (shifts it in time ahead).

var pow = ahead.shift(function (a, b) {
    return Math.pow(a, b);
});

Lets shift console.log in time ahead

var log = ahead.shift(console.log.bind(console));

Thrown errors will break the promise

var fail = ahead.shift(function () {
    throw Error("break everything");
});

All the above created functions can be used in a synchronous style but are executed asynchronous

log(pow(multiply(random(1000), 3), 2));

The returned value of each function created with ahead or ahead.shift is a promise for a future value

fail(random(1000), 3).then(
    function success (value) {
    },
    function fail (reason) {
    }
);