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

isolated-task-runner

v0.0.1

Published

Run invidual tasks on a seperate process

Downloads

3

Readme

task-runner

Task runner framework

Defining a task

A task is a single isolated module that exports an object with the following api:

// this is the "mytask" module
function myTask(options, callback) {
  // in the case of a non-deterministic error you simply
  // invoke the callback with one like in all node operations
  callback(new Error('....'));

  // and in the success case
  callback(null, outcome, { someData: true });
}

module.exports = myTask;

Invoking a task

var runner = require('isolated-task-runner');

runner.perform(
  require.resolve('myask'), /* module to run: use require.resolve to use npm packages */
  1000, /* timeout in ms */
  { somedata: true }, /* options to pass to task */
  function(err, outcome, result) {
    /* result of task */
  }
);

The callback takes a standard node-style error object, a boolean and an Object. The error object is a standard node error callback object. The boolean contains the outcome of the task. A true value means that the operation completely succeeded. A false value means that the operation failed and should be retried. The Object contains information relevant to status and reporting. The task running system will not make any choices based on the contents of this Object.

Isolation and error handling

  • Your task is run in a totally separate process and has no direct access the memory in the process where it was started.

  • Each task may fail (process dies, on the sync exception, off the async exception) and it will be handled gracefully and passed to the task runner.

  • Tasks should only generate errors when they fail non-deterministically. Deterministic failures should be noted by having an outcome of false. An api call that fails because the connection died should generate an error, where trying to comment on a bug that doesn't exist should have a false outcome