Adjust verbosity for individual grunt tasks
This plugin simply hooks until grunt.log.writeln
to allow you to cleanup log output.
This plugin requires Grunt ~0.4.0
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-verbosity --save-dev
One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-verbosity');
verbosity
taskIn your project's Gruntfile, add a section named verbosity
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
verbosity: {
// Default
option1: {
// options: { mode: 'hidden' },
tasks: ['copy']
},
// Output is rewritten on the line to show progress but save space
option2: {
options: { mode: 'oneline' },
tasks: ['copy:files']
},
// Output is normal. Useful for debugging without commenting out the whole block
option3: {
options: { mode: 'normal' },
tasks: ['copy:something']
}
},
})
Type: String
Default value: normal
A string value to determine how to modify grunt.log.writeln
output.
hidden
(Default): See the task get executed, but not its outputoneline
: See the output overwrite the same line to conserve spacenormal
: See the output without modification. Useful for debugging.dot
: See each line of output reduced to a dot to show progress.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.
verbosity.writeln
and undefined
Verbosity.match
not returning an arraygrunt.util.hooker
dot
mode - #1 (Thanks @getfatday!)