Grunt output should look consistent, and maybe even pretty. As such, there is a plethora of logging methods, and a few useful patterns. All of the methods that actually log something are chainable.
If msg string is omitted, logs ERROR in red, otherwise logs >> msg, with trailing newline.
T in grunt.log.CommonLogging<T>
Log an error with grunt.log.error, wrapping text to 80 columns using grunt.log.wraptext.
T in grunt.log.CommonLogging<T>
If msg string is omitted, logs OK in green, otherwise logs >> msg, with trailing newline.
T in grunt.log.CommonLogging<T>
Log an ok message with grunt.log.ok, wrapping text to 80 columns using grunt.log.wraptext.
T in grunt.log.CommonLogging<T>
Log the specified msg string in bold, with trailing newline.
T in grunt.log.CommonLogging<T>
Log the specified msg string, with no trailing newline.
T in grunt.log.CommonLogging<T>
Log a list of obj properties (good for debugging flags).
T in grunt.log.CommonLogging<T>
Log the specified msg string, with trailing newline.
T in grunt.log.CommonLogging<T>