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 ❤️ and support.
(TOC generated by verb using markdown-toc)
Install with npm:
$ npm install --save composerHeads up the .watch method was removed in version 0.11.0. If you need watch functionality, use base-tasks and base-watch.
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);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
name{String}: Name of the task to registeroptions{Object}: Options to set dependencies or control flow.options.deps{Object}: array of dependenciesoptions.flow{Object}: How this task will be executed with it's dependencies (series,parallel,settleSeries,settleParallel)deps{String|Array|Function}: Additional dependencies for this task.fn{Function}: Final function is the task to register.returns{Object}: Return the instance for chaining
Example
// register task "site" with composer
app.task('site', ['styles'], function() {
return app.src('templates/pages/*.hbs')
.pipe(app.dest('_gh_pages'));
});Params
tasks{String|Array}: Array of task names to build. (Defaults to[default]).options{Object}: Optional options object to merge onto each task's options when building.cb{Function}: Optional callback function to be called when all tasks are finished building. If omitted, a Promise is returned.returns{Promise}: Whencbis omitted, a Promise is returned that will resolve when the tasks are finished building.
Example
app.build('default', function(err, results) {
if (err) return console.error(err);
console.log(results);
});Params
tasks{String|Array|Function}: List of tasks by name, function, or array of names/functions.returns{Function}: Composed function that may take a callback function.
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
//=> doneParams
tasks{String|Array|Function}: List of tasks by name, function, or array of names/functions.returns{Function}: Composed function that may take a callback function.
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
//=> doneWhen 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.
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.
composer is an event emitter that may emit the following events:
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 => {});.app(object) - instance of Composer.status(string) - current build status[1], eitherregister,startingorfinished..date(object) - with a.startproperty indicating start time as aDateobject..hr(object) - with a.startproperty indicating the start time as anhrtimearray..duration(string) - that will provide the duration in a human readable format..diff(string) - diff between the start and end times..offset(string) offset between the start date and the starthrtime
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) => {});.status(string) - current status[2] of the task. May beregister,starting, orfinished.
.date(object) - has a.startproperty indicating the start time as aDateobject..hr(object) - has a.startproperty indicating the start time as anhrtimearray..duration(string) that will provide the duration in a human readable format..diff(string) that will provide the diff between the start and end times..offset(string) offset between the start date and the start hr time
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 => {});app: current composer instance running the buildbuild: current build runtime informationtask: current task instance running when the error occurredrun: current task runtime information
- Now requires Node.js v8.0 or higher
- Updates the events that are emitted and adds statuses to the objects emitted on the events. see issues #20 and #21
- Updates the event objects to expose human readable durations. see issue #23
- Removes unused properties. see issue #24
- Updates
.buildto return a promise when the callback is not passed in. see issue #28
- Updates bach to
1.0.0. - Errors emitted from inside a task now have the
'in task "foo":'prefixed to the error message. see issue #22 - Expose
.runInfoon the task object for use in event listeners and task functions. - Add
.durationto the.run/.runInfoobject that shows the duration in a human friendly format. This will also show the current duration from the time the task started to the time it's called if used inside a task function. see issue #23
app.task('foo', function(cb) {
console.log(this.runInfo.duration);
});- Skip tasks by setting the
options.skipoption to the name of the task or an array of task names. - Making additional
errproperties non-enumerable to cut down on error output.
- You can no longer get a task from the
.task()method by passing only the name. Instead dovar task = app.tasks[name]; - Passing only a name and no dependencies to
.task()will result in anooptask being created. optionsmay be passed to.build(),.series()and.parallel()optionspassed to.build()will be merged onto task options before running the task.- Skip tasks by setting their
options.runoption tofalse.
- Allow passing es2015 javascript generator functions to
.task().
- Allow using glob patterns for task dependencies.
- BREAKING CHANGE: Removed
.watch(). Watch functionality can be added to base applications using base-watch.
- Removes
session.
- Use
defaultwhen no tasks are passed to.build().
- Ensure task dependencies are unique.
- Emitting
taskwhen adding a task through.task() - Returning task when calling
.task(name)with only a name.
- Emitting
task:*events instead of generic*events. See event docs for more information.
- No longer returning the current task when
.task()is called without a name. - Throwing an error when
.task()is called without a name.
- Adding properties to
errinstances and emitting instead of emitting multiple parameters. - Adding series and parallel flows/methods.
- BREAKING CHANGE Renamed
.run()to.build()
.watchreturns an instance ofFSWatcher
- Currently running task returned when calling
.task()without a name.
- Add session-cache to enable per-task data contexts.
- Event bubbling/emitting changed.
- Initial release.
Contributing
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Running Tests
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 testBuilding docs
(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 && verbYou might also be interested in these projects:
- assemble: Get the rocks out of your socks! Assemble makes you fast at creating web projects… more | homepage
- base-tasks: base-methods plugin that provides a very thin wrapper around https://github.com/jonschlinkert/composer for adding task methods to… more | homepage
- generate: Command line tool and developer framework for scaffolding out new GitHub projects. Generate offers the… more | homepage
- update: Be scalable! Update is a new, open source developer framework and CLI for automating updates… more | homepage
- verb: Documentation generator for GitHub projects. Verb is extremely powerful, easy to use, and is used… more | homepage
| Commits | Contributor |
|---|---|
| 219 | doowb |
| 36 | jonschlinkert |
Brian Woodward
Copyright © 2018, Brian Woodward. Released under the MIT License.
This file was generated by verb-generate-readme, v0.6.0, on March 01, 2018.
- When `build.status` is `finished`, the `.hr` object also has `.duration` and `.diff` properties containing timing information calculated using `process.hrtime`. ↩
- When `task.status` is `finished`, the `.hr` object also has `.duration` and `.diff` properties containing timing information calculated using `process.hrtime`. ↩