Gathering detailed insights and metrics for grunt-concurrent
Gathering detailed insights and metrics for grunt-concurrent
Gathering detailed insights and metrics for grunt-concurrent
Gathering detailed insights and metrics for grunt-concurrent
npm install grunt-concurrent
Module System
Unable to determine the module system for this package.
Min. Node Version
Typescript Support
Node Version
NPM Version
798 Stars
86 Commits
66 Forks
15 Watching
1 Branches
13 Contributors
Updated on 12 Sept 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-21.4%
9,809
Compared to previous day
Last week
3.8%
61,673
Compared to previous week
Last month
-0.3%
266,260
Compared to previous month
Last year
-20.7%
3,372,089
Compared to previous year
4
1
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.
1npm install --save-dev grunt-concurrent
1require('load-grunt-tasks')(grunt); 2 3grunt.initConfig({ 4 concurrent: { 5 target1: ['coffee', 'sass'], 6 target2: ['jshint', 'mocha'] 7 } 8}); 9 10// Tasks of target1 run concurrently, after they all finished, tasks of target2 run concurrently, instead of target1 and target2 running concurrently. 11grunt.registerTask('default', ['concurrent:target1', 'concurrent:target2']);
1grunt.initConfig({ 2 concurrent: { 3 target: [['jshint', 'coffee'], 'sass'] 4 } 5});
Now jshint
will always be done before coffee
and sass
runs independent of both of them.
Type: number
Default: Twice the number of CPU cores with a minimum of 2
Limit how many tasks that are run concurrently.
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 concurrent: {
3 target: {
4 tasks: ['nodemon', 'watch'],
5 options: {
6 logConcurrentOutput: true
7 }
8 }
9 }
10});
11
12grunt.loadNpmTasks('grunt-concurrent');
13grunt.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.
Type: boolean
Default: true
You can optionally skip indenting the log output of your concurrent tasks by specifying false
. This can be useful for running tasks in parallel for a stdout parser which expects no indentation, for example, TeamCity tests.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 3/30 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More