Eats non-test console output

[bitmage]

Piping into tap-spec will sometimes eat my debug statements, depending on where they appear in the tap output. Other times the output will be there, but all my colored output gets translated to brown (on my terminal).

Is there any way to detect these non-tap output lines and pass them through unchanged? The spec seems to state that this should be normal operating procedure.

As a result of this, I'm currently not using a formatter, and regretting the choice to use tape (as I'm now having to stare at a machine readable output). The concept of tap output is lovely, but I can't do my work without debug statements.

[robwold]

To add to this, I've been trying it out with testdouble, a mocking library which raises an error if a function isn't called as expected and prints an incredibly useful debugging trace. tap-spec eats this information completely.