82249c99b3
Fixing up Grunt file to watch for directories Exclude node modules folder from Jekyll built site
1.9 KiB
grunt-concurrent 
Run grunt tasks concurrently
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
$ npm install --save-dev grunt-concurrent
Usage
require('load-grunt-tasks')(grunt); // npm install --save-dev load-grunt-tasks
grunt.initConfig({
concurrent: {
target1: ['coffee', 'sass'],
target2: ['jshint', 'mocha']
}
});
grunt.registerTask('default', ['concurrent:target1', 'concurrent:target2']);
Options
limit
Type: number
Default: Twice the number of CPU cores with a minimum of 2
Limit how many tasks that are run concurrently.
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:
grunt.initConfig({
concurrent: {
target: {
tasks: ['nodemon', 'watch'],
options: {
logConcurrentOutput: true
}
}
}
});
grunt.loadNpmTasks('grunt-concurrent');
grunt.registerTask('default', ['concurrent:target']);
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.
License
MIT © Sindre Sorhus