lukeed

Hi there, thanks for the write-up, and I'm sorry I never saw this before!

Unfortunately, there was a dispute between myself & the co-owner, which resulted in my forced removal. I authored all releases between 1.0 and 2.0, inclusive. You may find my continuation of the project as Taskr, found here: https://github.com/lukeed/taskr

As for your article, as of fly@2.0 and taskr@1.0, there have been a few major changes:

• I no longer recommend a global installation, although it will still work
• The core codebase is much lighter, so clear, concat, and watch have been extracted to plugins
• Task function definitions have changed

$ npm install --save-dev taskr fly-watch fly-clear fly-concat fly-browserify babelify

Note: Because taskr and fly are the same (I wrote it), the plugins are interchangeable.

export async function clean(task) {
  await task.clear(paths.dist);
}

export async function build(task, opts) {
  await task.start('clean');
  await task.source(opts.src || paths.scripts) // 'watch' sends changed files as opts.src
        .browserify({ transform:[require('babelify')] })
        .concat('your-lib.js')
        .target(paths.dist)
}

export default async function (task) {
    yield task.watch(paths.scripts, 'build');
}

The above example is using async/await thanks to the fly-esnext package, which I did not include in the preliminary installation list.

Thanks for the write-up!
Luke