endojs
SES: Log all lines of errors to Node.js stderr
All console output should ideally go to an out-of-band debugger or at least to process stderr. However, in Node.js, by dint of console.log("Hello, World!") being the canonical Node.js program rather than process.stdout.write('Hello, World!\n') or the XS print("Hello, World!\n") idiom, the log level goes to stdout so we can’t have nice things.
We need to iron out the tamed console so that every line goes to stderr. That may be coalescing multiple lines into single console.error calls, but I’m not entirely sure. For certain, console.error in at least Chrome has the additional behavior of incorporating of noting the stack of the console.error call site, which is generally less useful than the stack at the site of a logged error. We will need to fiddle with this in both Node.js and devtools until it does something similar to good.
@kriskowal This does not have an area label that is covered by our weekly tech / planning meetings. Can you assign the proper label? We cover: agd, agoric-cosmos, amm, core economy, cosmic-swingset, endo, getrun, governance, installation-bundling, metering, run-protocol, staking, swingset, swingset-runner, token economy, wallet, zoe contract,