I think having a separate isTerminal checking for stdout and stderr is necessary.
One use case for this is when running elm-make from nodejs, we can choose to ignore/pipe stdout, but not the stderr in order to keep the ansi color on the compiler error message, e.g.:
I think having a separate isTerminal checking for stdout and stderr is necessary. One use case for this is when running elm-make from nodejs, we can choose to ignore/pipe stdout, but not the stderr in order to keep the ansi color on the compiler error message, e.g.:
If we only check for stdout, in the above scenario, the compiler error message will be displayed without the ansi color.
I believe this PR will also solve this issue #70