Recipe (gulp 4): using gulp-hub as a custom registry for loading multiple gulpfiles

gulp-hub has been great at working with me to implement itself as a custom registry in support of gulp4. I really would like a recipe showing how to load multiple gulpfiles with gulp-hub as the registry.

Docs: https://github.com/frankwallis/gulp-hub/tree/4.0

[bradcerasani]

@phated Just tried a stripped down example explicitly ordering the tasks passed to gulp-hub, but build still doesn’t recognize the clean task as ever being defined (despite loading before it):

Even if it did work, manually declaring each filename and their order in the array passed to gulp-hub is a bit meticulous. I don’t see this as a problem with gulp-hub specifically (it does what it claims to), but rather gulp-hub as a replacement to the previous require-dir recipe for splitting tasks across multiple files.

Let me know if I should open a separate issue here - not sure if I’m doing something wrong but I’m happy to help update this recipe once sorted.

[mryellow]

We want to promote gulp-hub as the way to do this

It’s not meeting the functional requirements. Should only have to specify the task directory and have those tasks accessible from that point forward. Current implementation breaks down when it comes to nesting, at which point you’d be once again specifying each set of task dependencies for each file. Issue being that these dependencies are already clearly defined in the tasks themselves and using gulp-hub as it stands would result in double-handling with these being defined multiple times.