Playing around with Tup

package.json

{
  "name": "tup-demo",
  "version": "0.0.0",
  "description": "Playing around with using Tup as a build system",
  "dependencies": {},
  "devDependencies": {
    "coffee-script": "~1.7.1",
    "istanbul": "~0.2.6",
    "urequire": "~0.6.13-1"
  },
  "scripts": {},
  "author": "sean.copenhaver@gmail.com",
  "license": "MIT"
}

Tupfile

  : foreach app/*.coffee |> ./node_modules/coffee-script/bin/coffee -c -o _build/coffee/ %f |> _build/coffee/%B.js
  : foreach _build/coffee/*.coffee |> ./node_modules/istanbul/lib/cli.js --output _build/instrumented/ %f |> _build/instrumented/%B.js

Basically I was trying to install everything local to the project, using Tup to incrementally process the files, and keep all the files around so that Tup could quickly recompute any build outputs.

I'm not sure how clean tasks or other such task automation would work in Tup. That might be where doing all of this behind a basic Makefile might be good.

OK, after reading through the docs a little more and studying this example I think I get the mechanics of it now.