grunt-check_env v0.1.4
grunt-check_env
将指定(words)的关键字替换成自定义的关键字(replaceStr)
Getting Started
This plugin requires Grunt ~0.4.5
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-check_env --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-check_env');
The "check_env" task
Overview
In your project's Gruntfile, add a section named check_env
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
check_env: {
options: {
words: '',//被替换的关键字,支持一行多个单词替换
replaceStr:'',//替换后的关键字
},
your_target: {
// Target-specific file lists and/or options go here.
'key':[] //key:替换后生成文件的路径 []:数组格式化的文件支持三种格式,1.单个文件,文件夹,文件夹下面指定的文件格式 forexample 123.js tests/ test/*.js
}
}
});
Options
options.separator
Type: String
Default value: ', '
A string value that is used to do something with whatever.
options.punctuation
Type: String
Default value: '.'
A string value that is used to do something else with whatever else.
Usage Examples
Default Options
In this example, the default options are used to do something with whatever. So if the testing
file has the content Testing
and the 123
file had the content 1 2 3
, the generated result would be Testing, 1 2 3.
grunt.initConfig({
check_env: {
options: {},
files: {
'dest/default_options': ['src/testing', 'src/123'],
},
},
});
Custom Options
In this example, custom options are used to do something else with whatever else. So if the testing
file has the content Testing
and the 123
file had the content 1 2 3
, the generated result in this case would be Testing: 1 2 3 !!!
grunt.initConfig({
check_env: {
custom_options: {
options: {
words: 'uat',
replaceStr:'test',
file_path:''//文件路径
},
files: {
'tmp/custom_options': ['tests/*.js']//key 文件生成的目录,value 要格式化的文件支持三种格式,1.单个文件,文件夹,文件夹下面指定的文件格式 forexample 123.js tests/ test/*.js
}
}
}
});
Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
Release History
(Nothing yet)