
Security News
New CNAPulse Dashboard Tracks CNA Activity and Disclosure Trends
Open source dashboard CNAPulse tracks CVE Numbering Authorities’ publishing activity, highlighting trends and transparency across the CVE ecosystem.
grunt-generate-configs
Advanced tools


CLI to generate separate grunt configuration files automatically
This command will take your big, fat grunt configuration object and automatically generate separate files to store the task configuration objects in. It's a one time operation to be done before you start using load-grunt-configs
This plugin requires Grunt ~0.4.2
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-generate-configs
(There's no need for the --save flags, since this task should be run only once.)
Once the plugin has been installed, you can run it from the command line:
generate_configs
The command will parse your grunt configuration object and automatically create files for each task.
Now you can safely remove the module if you want:
npm uninstall grunt-generate-configs
--target=<dir> you can specify the output directory using the target-flag. E.g.: grunt generate_configs --target=foo will create a foo directory instead of config.--type=[js|json|coffee|yaml] allows you to output the configuration objects as json, yaml, coffee files or javascript modules.For example, if this is your grunt configuration inside Gruntfile.js:
grunt.initConfig({
jshint : {
all : [
'Gruntfile.js', 'tasks/*.js', '<%=nodeunit.tests%>'
],
options : {
jshintrc : '.jshintrc',
},
},
// Before generating any new files, remove any previously-created files.
clean : {
config : ['config'],
},
// Unit tests.
nodeunit : {
tests : ['tests/*_test.js'],
},
});
It will create the files jshint.json, clean.json and nodeunit.json inside a config directory, containing the configuration objects:
//file: config/jshint.json
{
"all": [
"Gruntfile.js",
"tasks/*.js",
"<%=nodeunit.tests%>"
],
"options": {
"jshintrc": ".jshintrc"
}
}
//file: config/clean.json
{
"config": [
"config"
]
}
//file: config/nodeunit.json
{
"tests": [
"tests/*_test.js"
]
}
Once these files are generated, use the load-grunt-configs module to automatically load all configuration files:
npm install load-grunt-configs --save-dev
and inside your Gruntfile.js replace the grunt configuration object with:
var configs = require('load-grunt-configs')(grunt);
grunt.initConfig(configs);
See the project for more information, options and examples: load-grunt-configs
Copyright (c) 2014 Camille Reynders Licensed under the MIT license.
FAQs
CLI to generate separate grunt configuration files automatically
We found that grunt-generate-configs demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Open source dashboard CNAPulse tracks CVE Numbering Authorities’ publishing activity, highlighting trends and transparency across the CVE ecosystem.

Product
Detect malware, unsafe data flows, and license issues in GitHub Actions with Socket’s new workflow scanning support.

Product
Add real-time Socket webhook events to your workflows to automatically receive pull request scan results and security alerts in real time.