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

mktask

v1.3.12

Published

Task runner

Downloads

46

Readme

Task Runner

Build Status npm version Coverage Status

Run build tasks

Runs named task functions that return streams, arrays of deferred task functions or invoke the callback function.

Install

Install the mkdoc tools for the mk program:

npm i -g mkdoc


Usage

Create a mkdoc.js task file like this one (source file):

var mk = require('mktask');

// @task readme build the readme file.
function readme(cb) {
  mk.doc('doc/readme.md')         // read markdown source document
    .pipe(mk.pi())                // parse processing instructions
    .pipe(mk.ref())               // include link references
    .pipe(mk.abs())               // make links absolute
    .pipe(mk.msg())               // append generator message
    .pipe(mk.toc({depth: 2}))     // inject table of contents list
    .pipe(mk.out())               // convert abstract syntax tree to markdown
    .pipe(mk.dest('README.md'))   // write the result to a file
    .on('finish', cb);            // proceed to next task
}

mk.task(readme);

Note that you should not install the mktask dependency, it is resolved by the command line program.

Example

Build all tasks (or a main task when defined):

mk

Build specific tasks:

mk api readme

Use a specific build file:

mk -f ~/mkdoc.js readme

To see a list of tasks use:

mk --tasks

Guide

This guides assumes you are using the mk program to run tasks, install it with npm i -g mkdoc.

Creating Tasks

Tasks are named functions that are passed to the task function:

var mk = require('mktask');

// @task readme build the readme file.
function readme(cb) {
  // implement task logic
  cb();
}

mk.task(readme);

Anonymous functions are not allowed and will generate an error if used.

Task Documentation

It is considered good practice to annotate your tasks with comments that provide a name and description of the task so that it will be included in the list printed when running mk --tasks.

// @task readme build the readme file.

Task Names

By default the task identifier (referenced on the command line) is taken from the function name but you may explicitly specify an identifier if you prefer:

mk.task('docs', function readme(cb){cb()});

If you have dependencies the identifier comes afterwards:

mk.task([api, example], 'docs', function readme(cb){cb()});

When multiple tasks are passed then the identifier is taken from the last function which in this case becomes readme:

mk.task(function api(cb){cb()}, function readme(cb){cb()});

Main Task

The mk program when executed with no arguments will either run all available tasks in series or a main task if declared. To declare a main task give it the name main:

var mk = require('mktask');

// @task main build all documentation.
function main(cb) {
  // implement task logic
  cb();
}

mk.task(main);

Deferred Tasks

Typically task functions will invoke the callback function when done but they may also return an array of task functions which is useful when a task wishes to defer to a series of other tasks:

var mk = require('mktask');

// @task api build the api docs.
function api(cb) {
  // implement api task logic
  cb();
}

// @task readme build the readme file.
function readme(cb) {
  // implement readme task logic
  cb();
}

// @task main build the api and readme docs.
function main() {
  return [api, readme];
}

mk.task(api);
mk.task(readme);
mk.task(main);

Note that when deferring to other task functions they must have been registered by calling task().

Stream Tasks

Sometimes when creating complex stream pipelines it is useful to return streams so that parts of the pipeline become reusable between tasks, for example:

var mk = require('mktask')
  , ast = require('mkast');

function in() {
  return mk
    .src('This is a markdown paragraph.')
    .pipe(ast.stringify());
}

function out() {
  return mk.dest('target/stream-example.md');
}

mk.task(in, out);

When a task returns a stream it is piped to the next task function in the pipeline and the callback function is added as a listener for the finish event on the last stream in the pipeline.

Task Dependencies

Task functions may declare an array of functions to call before the task function(s).

Dependencies are executed in parallel but they must all complete before the tasks are executed:

var mk = require('mktask');

// @task api build the api docs.
function api(
  // implement api task logic
  cb();
}

// @task example build the example file.
function example(
  // implement example task logic
  cb();
}

// @task readme build the readme file.
function readme(cb) {
  // implement readme task logic
  cb();
}

mk.task([api, example], readme);

Task Arguments

Task functions are automatically exposed the parsed arguments object via this.args such that mk readme --env devel would result in the readme task being able to access the env option using this.args.options.env.

Flags are available in this.args.flags such that mk readme -v yields true for this.args.flags.v.

Note that some command line arguments are handled by the mk program you should take care that the names do not conflict.

For detailed information on the args object see the argparse library.

Sample

Inline code examples from the working example in /doc/example.

The build file mkdoc.js:

var mk = require('../../index');

// @task example build the example file.
function example(cb) {
  mk.doc('source.md')             // read markdown source document
    .pipe(mk.pi())                // parse processing instructions
    .pipe(mk.ref())               // include link references
    .pipe(mk.out())               // convert abstract syntax tree to markdown
    .pipe(process.stdout)         // print the result
    .on('finish', cb);            // proceed to next task
}

mk.task(example);

The input source file source.md:

# Source

Example for the mk(1) program supplied by [mkdoc][].

A paragraph of markdown text followed by an include processing instruction.

<? @include include.md ?>

Followed by some more markdown content and the result of executing a shell command:

<? @exec uname ?>

Finally include the link definition file.

<? @include links.md ?>

Include file include.md:

## Include

A file that was included from another markdown document.

Include file links.md:

[mkdoc]: https://github.com/mkdoc/mkdoc

Result:

# Source

Example for the mk(1) program supplied by [mkdoc][].

A paragraph of markdown text followed by an include processing instruction.

## Include

A file that was included from another markdown document.

Followed by some more markdown content and the result of executing a shell command:

Linux

Finally include the link definition file.

[mkdoc]: https://github.com/mkdoc/mkdoc

Help

Usage: mk [-h] [--tasks] [--help] [--version] [--file=<file...>] [task...]

  Task runner.

Options
  -f, --file=[FILE...]    Load specific task files
  --tasks                 Print task list
  -h, --help              Display help and exit
  --version               Print the version and exit

[email protected]

API

mk

mk()

Creates a task collection.

Returns a Task.

#task

static task()

Adds a task to the default task collection.

Returns a Task.

Task

Task()

Encapsulates a collection of named task functions.

.task

Task.prototype.task()

Adds task function(s) to the list of known tasks.

.get

Task.prototype.get()

Get a task map by function reference.

Returns a task map if found.

.run

Task.prototype.run()

Gets a task runner for this collection of tasks.

Returns a task Runner.

#src

static src()

Parses a markdown string into a stream.

Returns the output stream.

#dest

static dest([file])

Get a destination output stream.

If the file option is not given a destination stream that prints to stdout is returned.

Returns an output stream.

  • file String path to the output file.

runner

runner(opts)

Get a task runner.

Returns a Runner.

  • opts Object processing options.

Runner

new Runner(opts)

Execute task functions.

  • opts Object processing options.

Options

  • task Object collection of tasks.

.get

Runner.prototype.get(id)

Get a task by name identifier.

Returns a task or undefined.

  • id Function|String task identifier.

.series

Runner.prototype.series(list, cb)

Execute task functions in series.

  • list Array of task functions.
  • cb Function callback function.

.parallel

Runner.prototype.parallel(list[, concurrent], cb)

Execute task functions in parallel.

  • list Array of task functions.
  • concurrent Number number of concurrent calls.
  • cb Function callback function.

.resolve

Runner.prototype.resolve(cb)

Resolves dependencies for a task.

Searches for dependencies that are tasks and injects any dependencies for located tasks.

Returns an array of task dependencies.

  • cb Function callback function.

.exec

Runner.prototype.exec(id, cb)

Execute a task by name identifier.

Dependencies are run in parallel before task execution.

Returns a task or undefined.

  • id Function|String task identifier.
  • cb Function callback function.

.each

Runner.prototype.each([names], cb)

Execute a list of tasks.

When names is not given and no main task exists all tasks are executed; if a main task exists it is executed.

  • names Array list of task identifiers or task functions.
  • cb Function callback function.

License

MIT


Created by mkdoc on May 22, 2016