Add the ability to dynamically modify transforms to barback.

pkg/barback/lib/src/package_graph.dart

Index: pkg/barback/lib/src/package_graph.dart
diff --git a/pkg/barback/lib/src/package_graph.dart b/pkg/barback/lib/src/package_graph.dart
index 639deea6f49300cb47f6e4729e07d787a45a93e6..85c250b38219402403dbe18228752859a90a2f89 100644
--- a/pkg/barback/lib/src/package_graph.dart
+++ b/pkg/barback/lib/src/package_graph.dart
@@ -56,8 +56,7 @@ class PackageGraph {
   /// made available by [provider].
   PackageGraph(this.provider) {
     for (var package in provider.packages) {
-      var cascade = new AssetCascade(this, package,
-          provider.getTransformers(package));
+      var cascade = new AssetCascade(this, package);
       // The initial result for each cascade is "success" since the cascade
       // doesn't start building until some source in that graph is updated.
       _cascadeResults[package] = new BuildResult.success();
@@ -115,4 +114,10 @@ class PackageGraph {
       cascade.removeSources(ids);
     });
   }
+
+  void updateTransformers(String package,
+      Iterable<Iterable<Transformer>> transformers) {
+    _cascadeResults[package] = null;

[Bob Nystrom, 2013/08/20 19:08:54]

What if the set of transformers are unchanged?

[nweiz, 2013/08/20 21:39:17]

We always want to trigger a rebuild so that the caller can consistently expect
that [updateTransformers] will cause [results] to emit a result at some point in
the future.

[Bob Nystrom, 2013/08/20 22:18:12]

Ensuring a result is sent is fine, but it sucks to discard the previously
generated assets and actually apply all of the transformers again from scratch.
Isn't there a way we can do the former without the latter?

+    _cascades[package].updateTransformers(transformers);
+  }
 }