A dependency-resolving plugin for Gulp. It grabs all files related to one modification to building system.
Gulp provides incremental building.
However it is agnostic about the dependencies among files.
child.jade depends on
parent.jade, then whenever
child should be recompiled as well.
Existing gulp plugins do not support this. Or one could fall back on
gulp-progeny aims to solve this. If
parent.jade is edited and passed to
gulp-progeny, all files that recursively depends on that file will be collected by
progeny and are passed to succesive building stream.
What does gulp-progeny do
This plugin brings the agility of brunch to gulp world.
It provides generic dependency detection to various file types.
progeny parses files by grepping specific
import statements, and builds dependency trees for building tasks.
So it just use Regular Expression to extract dependency information. This simple solution is fast and dirty, but also working.
gulp-progeny out of box supports
To exploit the power of
gulp-cached in tandem.
var cache = ;var progeny = ;var stylus = ;gulp;gulp;
cached will pass all files to
progeny in the first run, which enables dependency tree building,
just pass changed files later for incremental building.
progeny in its core, please see their configuration docs for the options that can be used with this plugin.
gulp-progeny, by the virtue of its design, has following limitations.
Filenames must be static in source code. Otherwise regexp fails to work.
Sass/Scss filenames should not contain apostrophes. This limitation is due toSass's multiple import feature. Matching filenames with
'"is far beyond the reach of regular expressions with only one match, which is the format used in this plug in.
Limitations above are almost ineluctable for this simple plugin. To keep API and extension simple and generic, some features are doomed to be dropped. This plugin does not fill the chasm between a single one Regexp and full-bloom parsers.