Scripts Loader (Gulp.js tasks loader/manifest)

Walk directory recursive and load all the scripts from there. (Super helpful when you want to separate your big gulp file into standalone tasks and load each task very easily.)

Usage

This example will demonstrate how to use scripts-loader with Gulp.js. Folder structure

-
--src
--node_modules
--gulp
---tasks
----client
-----app.coffee
-----lib.coffee
----server
-----app.coffee
-----lib.coffee
----default.coffee
---index.coffee
---config.coffee
--test
--gulpfile.coffee

Yes. Gulp.js finally supports coffee syntax for gulpfile configuration.

gulpfile.coffee

require './gulp'

gulp/index.coffee (SCRIPTS-LOADER SETTINGS)

scriptsLoader = require 'scripts-loader'

config = require './config'

scriptsLoader.load config.root + '/gulp/tasks', {
    verbose : false
    endings : 'js|coffee'
}

gulp/config.coffee

config = {
    env : null

    root : __dirname + '/..'
}

module.exports = config

gulp/tasks/client/lib.coffee (GULP TASK DECLERATION)

gulp = require 'gulp'
bowerFiles = require 'main-bower-files'
concat = require 'gulp-concat'

dictionaries = require '../../dictionaries'
config = require '../../config'

gulp.task 'client/lib', ->

    gulp.src bowerFiles(env: config.env)
        .pipe(concat("1_lib.js"))
        .pipe(gulp.dest(dictionaries.dest.public + '/js/'))

gulp/tasks/default.coffee

gulp = require 'gulp'

gulp.task 'defualt', ['server/lib', 'server/app', 'client/lib', 'client/app']

Motivation

Yeah... We've got 2015 today. And I still can see gulpfile.js files which have more than 1k lines per file over the internet. And that makes me a little bit worried because we've got such great tools but we don't using them in a good way (fortunately we can see an exceptions and that is great of course).

Above I suggest how to separate huge gulpfile into standalone tasks and make building process clean and easily understandable.

Plus you can use this library for quick load all of gulp files.

Thanks for your pull requests and questions!!