grunt-concurrentdep

Run grunt tasks concurrently by depends

Running slow tasks like Coffee and Sass concurrently can potentially improve your build time significantly. This task is also useful if you need to run multiple blocking tasks like nodemon and watch at once.

Install

1$ npm install --save-dev grunt-concurrentdep

Usage

1require('jit-grunt')(grunt); // npm install --save-dev jit-grunt
2
3grunt.initConfig({
4    concurrentdep: {
5        app: {
6            concat: ['csslint','jshint'],
7            cssmin: ['concat'],
8            csslint: ['preprocess'],
9            jshint: ['preprocess'],
10            uglify: ['concat'],
11            phplint: []
12        }
13    }
14});
15
16grunt.registerTask( "default",['concurrentdep']);

                        ┌ csslint ┐        ┌ uglify ┐
run:       ┌ preprocess ┤         ├ concat ┤        ├┐
     start ┤            └ jshint ─┘        └ cssmin ┘├ done
           └ phplint ────────────────────────────────┘

Options

limit

Type: number
Default: 4

Limit how many tasks that are run concurrently.

showDuration

Type: boolean
Default: true

You can optionally show taskduration

logConcurrentOutput

Type: boolean
Default: false

You can optionally log the output of your concurrent tasks by specifying the logConcurrentOutput option. Here is an example config which runs grunt-nodemon to launch and monitor a node server and grunt-contrib-watch to watch for asset changes all in one terminal tab:

1grunt.initConfig({
2    concurrentdep: {
3        options: {
4            logConcurrentOutput: true
5        },
6        app: {
7            ...
8        }
9    }
10});
11
12grunt.loadNpmTasks('grunt-concurrentdep');
13grunt.registerTask('default', ['concurrentdep:app']);

The output will be messy when combining certain tasks. This option is best used with tasks that don't exit like watch and nodemon to monitor the output of long-running concurrent tasks.

Based on grunt-concurrent