title: Gulp task module export declaration
body: <p>A lot of examples of gulp setups are using the common JS pattern. Gulp tasks are defined follows:</p>
  
  <p><strong>myGulpTask.js</strong></p>
  
  <pre><code>const gulp = require('gulp');
  
  const paths = {
      src = './src',
      dest = './dest'
  }
  
  const myGulpTask = function() {
  
      return gulp.src(paths.srcFoo)
          .pipe() // do stuff
          .pipe(gulp.dest(paths.dest));
  }
  
  module.exports = myGulpTask;
  gulp.task('my-gulp-task', myGulpTask);
  </code></pre>
  
  <p>This allows you to use this gulp task using: </p>
  
  <p><code>$ npm run gulp myGulpTask</code></p>
  
  <p>But since the task is directly assigned, would it make sense to define the export as follows:</p>
  
  <pre><code>//...
  const myGulpTask = module.exports = function() {
  
      return gulp.src(paths.srcFoo)
          .pipe() // do stuff
          .pipe(gulp.dest(paths.dest))
  }
  
  gulp.task('my-gulp-task', myGulpTask);
  //...
  </code></pre>
  
  <p>Maybe it's sweating the small stuff, or is there a difference in these two module declarations?</p>