As of #26, we can now write client errors to stderr, but server errors are still written to stdout because they're written to a single stream (the socket stream).
The idea is that we should be able to tell the client to write this string to stderr instead of stdout:
|
fail(con, String(err), exitCode); |
In order to support that, I imagine that we'd need to add some structure to what gets written in the connection (which would be yet another breaking change). We can probably make it backwards compatible though (at least for people using the node.js client, folks manually connecting to the TCP socket would have a harder time). What do you think?
As of #26, we can now write client errors to stderr, but server errors are still written to stdout because they're written to a single stream (the socket stream).
The idea is that we should be able to tell the client to write this string to stderr instead of stdout:
core_d.js/lib/server.js
Line 88 in 05990e7
In order to support that, I imagine that we'd need to add some structure to what gets written in the connection (which would be yet another breaking change). We can probably make it backwards compatible though (at least for people using the node.js client, folks manually connecting to the TCP socket would have a harder time). What do you think?