#External Task Groups in Gulp.
###Goal:
Create a group of reusable tasks as a fully seperate module, that can maintain their dependencies, and be integrated into many other projects. The reason to extenalize these, is for a few reasons. Firstly, I Imagine this as a private module for myself or my shop to use. In some ways it violates the modularity of existing npm modules. This isnt a single purpose item sporting the usual prefix gulp-whatever
. Another reason is it allows to keep a standardized stask list for a shop up to date across multiple projects, without duplicating the code in many projects. In our case, we have some frontend devops tasks , such as complxity analysis, hintling, linting, test runnign and so on. We want to be able to maintain that process, while giving everyone a similar entry point. If we improve the 'shops devops tooling' it would be nice to not have to go to every single project and add more code. Finally, this allows the quite large list of gulp- dependencies in the npm file to