endojs
Base console level
Per a tip from @michaelfig:
The BASE_CONSOLE_LEVEL in SES is currently “debug”, which unfortunately is “stdout” on Node.js. On Node.js, “warn” would be better since they go to “stderr”. However, in the browser, log levels have differentiating coloring, especially warn and error.
We may need to parameterize the base console log level by surrounding platform hints (read: presence of globalThis.process) and give users an override.
We might alternately need to rethink console taming. We already at least need to provide a mechanism for sending some logs to Ava t.log.
If we could somehow require('console') in node only, maybe we could build a new Console solely from stderr to use as the output stream? Of course there is the pesky issue of not being able to depend on a specific environment in the first place.
@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,
@kriskowal @michaelfig 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, ui, wallet, zoe, zoe contract
I’ve created a ses label that I would like to add to grooming under the endo umbrella, to differentiate the Hardened JavaScript (ses) from Distributed Hardened JavaScript (endo).