<story><title>No more `grunt watch` – faster builds with the Broccoli asset pipeline</title><url>http://www.solitr.com/blog/2014/02/broccoli-first-release/index.html</url><text></text></story><parent_chain></parent_chain><comment><author>munificent</author><text>This is slightly related and I don&amp;#x27;t want to sound like I&amp;#x27;m trying steal its thunder, because this looks really cool. I work on the asset pipeline that comes with the Dart SDK. It has many of the same principles as these.&lt;p&gt;Any transformation step can read in many input files and produce many output files. The built-in dev server tracks the entire asset dependency graph and only rebuilds the assets that are dirtied by a source file changing.&lt;p&gt;We have a plug-in system, and it&amp;#x27;s built on top of the same package management system that the SDK uses, so you can get transformer plug-ins as easily as you can get any other dependency.&lt;p&gt;We still have a lot of work to do to fully flesh things out, but it already does a lot, including supporting complex scenarios like transformers whose own code is the output of a previous transformer.&lt;p&gt;More here: &lt;a href=&quot;https://www.dartlang.org/tools/pub/assets-and-transformers.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.dartlang.org&amp;#x2F;tools&amp;#x2F;pub&amp;#x2F;assets-and-transformers.h...&lt;/a&gt;</text></comment>
<story><title>No more `grunt watch` – faster builds with the Broccoli asset pipeline</title><url>http://www.solitr.com/blog/2014/02/broccoli-first-release/index.html</url><text></text></story><parent_chain></parent_chain><comment><author>JangoSteve</author><text>&lt;i&gt;Broccoli is a new build tool. It’s comparable to the Rails asset pipeline in scope, though it runs on Node and is backend-agnostic.&lt;/i&gt;&lt;p&gt;This first line is a little disingenuous. Technically, it&amp;#x27;s not backend-agnostic, since it depends on Node being installed on the backend (in the same way that Sprockets [1] depends on Ruby). The Rails asset pipeline is a framework-specific integration of Sprockets. In much the same way, you could more closely integrate Broccoli with Rails if you wanted and call it a new Rails asset pipeline.&lt;p&gt;The project itself looks great, just the first line was confusing since they started the docs off by comparing apples to oranges.&lt;p&gt;A better comparison would probably be, &amp;quot;It&amp;#x27;s comparable to Sprockets (which powers the Rails asset pipeline), but runs on Node instead of Ruby.&amp;quot;&lt;p&gt;[1] &lt;a href=&quot;https://github.com/sstephenson/sprockets&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sstephenson&amp;#x2F;sprockets&lt;/a&gt;</text></comment>