Closed Riobe closed 9 years ago
After doing further research (and reading the code of the task itself which didn't look like it could possibly create this issue) I found that the problem is due to this issue. on grunt-concurrent.
This is not a problem with grunt-nodemon. When I run grunt-nodemon without running it through grunt-concurrent, it works perfectly.
I am using the npm debug module for debug logging and when I run nodemon itself it works fine and outputs in color. This makes it very easy to see different filters visually.
When I run how I expect is the same way using grunt and grunt-nodemon the color output is lost. Is there a way to get it back?
Here is an example:
Here is my Gruntfile.js: http://pastebin.com/6ityXi8v
I'm running using cygwin on Windows 8.1 with the following dependencies: $ npm list --depth=0 spell-gen@0.0.1 D:\Dev\NodeJs\spell-gen ├── body-parser@1.13.3 ├── cookie-parser@1.3.5 ├── debug@2.2.0 ├── express@4.13.2 ├── grunt@0.4.5 ├── grunt-concurrent@2.0.1 ├── grunt-contrib-jshint@0.11.2 ├── grunt-contrib-less@1.0.1 ├── grunt-contrib-uglify@0.9.1 ├── grunt-node-inspector@0.2.0 ├── grunt-nodemon@0.4.0 ├── jade@1.11.0 ├── matchdep@0.3.0 ├── mongoose@4.1.0 ├── morgan@1.6.1 └── serve-favicon@2.3.0