Here's an example of a GruntFile for a "clean" task (using the grunt-contrib-clean plugin):
clean: { dry: { src: ["build/css"], options: { 'no-write': true } } }
Running grunt clean:dry will output:
Running "clean:dry" (clean) task >> 2 paths cleaned. Done, without errors.
Using grunt clean:dry -v give me what I want:
Running "clean:dry" (clean) task Not actually cleaning live/css... Not actually cleaning live/js...
... but also displays a lot of configuration logs that have nothing to do with the current task. Can I use the -verbose flag (or something else) to display the complete output of the task without having to scroll through all the unrelated configuration logs?
PS: My other plugins suffer from the same problem, displaying only one line of output when their documentation indicates that I should expect more.
(Related questions: Record from grunt-contrib-jasmine and How to make JSHint work in grunt always use the --verbose checkbox does not answer this question).
gruntjs grunt-cli
Stevethemacguy
source share