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

dogmise

v2.0.2

Published

Directed acyclic graph of promises.

Downloads

1

Readme

dagmise

A directed acyclic graph of promises.

Example

var whenode = require('when/node');
var fs = whenode.liftAll(require('fs')); // make node fs functions promise like
var marked = require('marked');
var jade = require('jade');

dag.task('contents.md', function () {
    return fs.readFile('contents.md', 'utf8').then(marked);
});

dag.task('template.jade', function () {
    // resolve to a comiled jade template that we can later pass the rendered markdown as locals to.
    return fs.readFile('template.jade', 'utf8').then(jade.compile);
});

// index.html depends on contents.md and template.jade
dag.task('index.html', ['contents.md', 'template.jade'],
    function (target, contents, template) {
        // target === 'index.html'
        return fs.writeFile(target, template({ contents: contents }));
    });

dag.make('index.html')
.then(console.log)
.catch(console.error);

dag.make returns a pending promise that will be resolved when 'index.html''s task and all its depenencies have been resolved.

When a task is executed when walking the graph for dependencies, the node's value (see dager) is replaced by the promise, so subsequent visits to the node will not trigger repeated execution of the task, instead they will yield the same promise it gave the first time. For this reason, running make again will produce the same value, without reexecution of any of the tasks.

dag.update('node') will revert the node's task and those of the nodes that depend on that task to their unrun starting state. dag.reset() will revert all the nodes. These methods are synchronous and only succeed if there are no "makes" in progress. Their return value is a boolean indicating success or failure.