Ahh… just lost the comment I typed out… rewriting.

I had the same thought when I just this example. I see it both ways. I approached this trying to abstract as much as possible from these 3 plugins and I may have been a little overzealous.

The case for putting the wrapper in `gulp-handlebars` is that it's pretty specific to the plugin and arguably you can't do anything with the output of the plugin if you haven't wrapped it yet. Also, the result is still a function either way.

The case for putting it in `gulp-define-module` is that it access `Handlebars`, and as you mentioned before, you'd then need a `require` in there. Also, it does achieve a little more abstraction. Finally, `gulp-handlebars` could be seen only as a compiler, so it should handle just that one thing.

Honestly, I think both are "right" and I have no problem with it either way.