This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 45
Print errors to stderr instead of stdout #70
Comments
@rtfeldman can you provide example for your case so I can reproduce your problem? |
Sure, just take a look at https://travis-ci.org/rtfeldman/node-elm-test - it currently works as described above. 😃 |
@rtfeldman that was fast 👍 thanks |
On the other hand, #32 argues that the success messages should go to |
True, but it argues that based on an explicitly unsupported motivating use case. I commented over there. |
Tracked in #98 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In elm-test we generate a temporary .js file for the compiled
Test.elm
before running the tests.By default that means we get output like this every time the tests run:
This is pretty ugly, so what we've been doing is piping
elm-make
's stdout and discarding lines that start with "Success". This works, but introduces a new problem: because we're piping the output instead of just givingelm-make
direct access to the console, we miss out on colorized error messages. (Thanks @evancz for pointing out the culprit!)If
elm-make
wrote error messages tostderr
and success messages tostdout
, we could continue to pipe thestdout
stream for filtering, but letstderr
pass through as normal (colors and all), meaning everything would be rad and awesome!The text was updated successfully, but these errors were encountered: