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

yantr

v0.0.5

Published

Yet Another Node Task Runner

Downloads

4

Readme

Yantr

Yet Another Node Task Runner

This library is about dependent tasks and their resolution in correct order.

Constructor expects a collection of task objects. Task object basically just a plain js object with tags, depends and payload fields; tags - array of tags belong to this object, depends - tags on what this object is dependent, payload - async function with one callback argument. You should call callback in order to mark current task as done. Execution stops immediately if you provide error to the callback.

To start execution you should call run method on constructed Yantr object. run expects callback as its single argument. If error occurs during execution it will be passed to the callback. Yantr also checks provided graph for cyclic dependencies and generates error if any.

Notice that you should have at least one task without dependencies in order be able to resolve dependency tree. E.g.

var Yantr = require('./index.js');

var tasks = [
  {
    tags: [],
    depends: ['test'],
    payload: function (cb) {
      log('Hello tags!');
      cb();
    }
  },
  {
    tags: ['test', 'hello'],
    depends: [],
    payload: function (cb) {
      log('Hello');
      cb();
    }
  },
  {
    tags: ['test', 'world'],
    depends: ['hello', 'space'],
    payload: function (cb) {
      log('world!');
      cb();
    }
  },
  {
    tags: ['test', 'space'],
    depends: ['hello'],
    payload: function (cb) {
      log('_');
      cb();
    }
  },
  {
    tags: [],
    depends: ['hello', 'space', 'world'],
    payload: function (cb) {
      log('Hello world!');
      cb();
    }
  },
];

Yantr(tasks).run(function (e) {
  log(e? e:'Done!');
});

Following code will generate error because of circular dependencies:

var tasks = [
  {
    tags: ['A'],
    depends: ['B'],
    payload: function (cb) {
      log('Hello tags!');
      cb();
    }
  },
  {
    tags: ['B'],
    depends: ['C'],
    payload: function (cb) {
      log('Hello tags!');
      cb();
    }
  },
  {
    tags: ['C'],
    depends: ['A'],
    payload: function (cb) {
      log('Hello tags!');
      cb();
    }
  },
];