Home

Awesome

composer NPM version NPM monthly downloads NPM total downloads Linux Build Status Windows Build Status

API-first task runner with three methods: task, run and watch.

Please consider following this project's author, Brian Woodward, and consider starring the project to show your :heart: and support.

(TOC generated by verb using markdown-toc)

Install

Install with npm:

$ npm install --save composer

Heads up the .watch method was removed in version 0.11.0. If you need watch functionality, use base-tasks and base-watch.

Usage

const Composer = require('composer');
const composer = new Composer();

composer.task('default', cb => {
  console.log('Task: ', this.name);
  cb();
});

composer.build('default')
  .then(() => console.log('done!'))
  .catch(console.error);

API

Example

const composer = new Composer();

Dependencies may also be specified as a glob pattern. Be aware that the order cannot be guarenteed when using a glob pattern.

Params

Example

// register task "site" with composer
app.task('site', ['styles'], function() {
  return app.src('templates/pages/*.hbs')
    .pipe(app.dest('_gh_pages'));
});

Params

Example

app.build('default', function(err, results) {
  if (err) return console.error(err);
  console.log(results);
});

Params

Example

app.task('foo', function(done) {
  console.log('this is foo');
  done();
});

const fn = app.series('foo', function bar(done) {
  console.log('this is bar');
  done();
});

fn(function(err) {
  if (err) return console.error(err);
  console.log('done');
});
//=> this is foo
//=> this is bar
//=> done

Params

Example

app.task('foo', function(done) {
  setTimeout(function() {
    console.log('this is foo');
    done();
  }, 500);
});

const fn = app.parallel('foo', function bar(done) {
  console.log('this is bar');
  done();
});

fn(function(err) {
  if (err) return console.error(err);
  console.log('done');
});
//=> this is bar
//=> this is foo
//=> done

Task execution

When an individual task is run, a new Run instance is created with start, end, and duration information. This run object is emitted with some events and also exposed on the task instance as the .runInfo property.

properties

The run instance has the the following properties

.date

The .date property is an object containing the .start and .end date timestamps created with new Date().

.hr

The .hr property is an object containing the .start, .end and .duration properties that are created by using process.hrtime(). These properties are the actual arrays returned from process.hrtime(). There is also .diff and .offset computed properties that use the other properties to calculate the difference between .start and .end times (.diff) and the offset (error for time calculations) between the .duration and the .diff (this is usually very small).

.duration

The .duration property is a computed property that uses pretty-time to format the .hr.duration value into a human readable format.

Events

composer is an event emitter that may emit the following events:

build

This event is emitted when the build is starting and when it's finished. The event emits an object containing the build runtime information.

app.on('build', build => {});

build properties

task

This event is emitted when the task is registered, starting, and when it's finished. The event emits 2 arguments, the current instance of the task object and an object containing the task runtime information.

app.on('task', (task, run) => {});

task properties

run properties

error

This event is emitted when an error occurrs during a build. The event emits an Error object with extra properties for debugging the build and task that were running when the error occurred.

app.on('error', err => {});

err properties

History

v2.0.0

v1.0.0

v0.14.0

app.task('foo', function(cb) {
  console.log(this.runInfo.duration);
});

v0.13.0

v0.12.0

v0.11.3

v0.11.2

v0.11.0

v0.10.0

v0.9.0

v0.8.4

v0.8.2

v0.8.0

v0.7.0

v0.6.0

v0.5.0

v0.4.2

v0.4.1

v0.4.0

v0.3.0

v0.1.0

About

<details> <summary><strong>Contributing</strong></summary>

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

</details> <details> <summary><strong>Running Tests</strong></summary>

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test
</details> <details> <summary><strong>Building docs</strong></summary>

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb
</details>

Related projects

You might also be interested in these projects:

Contributors

CommitsContributor
219doowb
36jonschlinkert

Author

Brian Woodward

License

Copyright © 2018, Brian Woodward. Released under the MIT License.


This file was generated by verb-generate-readme, v0.6.0, on March 01, 2018.

<hr class="footnotes-sep"> <section class="footnotes"> <ol class="footnotes-list"> <li id="fn1" class="footnote-item">When `build.status` is `finished`, the `.hr` object also has `.duration` and `.diff` properties containing timing information calculated using `process.hrtime`. <a href="#fnref1" class="footnote-backref">↩</a> </li> <li id="fn2" class="footnote-item">When `task.status` is `finished`, the `.hr` object also has `.duration` and `.diff` properties containing timing information calculated using `process.hrtime`. <a href="#fnref2" class="footnote-backref">↩</a> </li> </ol> </section>