Michael Arnaldi

@sheremet-va while it may be useful we will be migrating to esm only shortly

Tested, doesn't seem to make a big difference. Also Effect is zero dependency and with perfectly working ESM modules so not sure that flag even counts in my case

@datner Thanks for the provoking comment, it is great to see people silently waiting for the rocket launch :) the reason can be basically reduced to: "it's my fault" I've...

Solved in main for next, need to backport

30/06/2023

31/12/2023

> OTEL auto instrumentation doesn't support ESM yet, should that be waited for? > > [open-telemetry/opentelemetry-js#1946](https://github.com/open-telemetry/opentelemetry-js/issues/1946) > > [open-telemetry/opentelemetry-js#1946 (comment)](https://github.com/open-telemetry/opentelemetry-js/issues/1946#issuecomment-1295493673) > > Note that, manual instrumentation works fine. When chatting...

Also check why the schedule input doesn't appear to be contravariant, i.e. if `E = HttpError | JsonError` and Schedule accepts `{ _tag: string }` it should work

What do you mean by branching? like conditional logic? also `Do` is a `TS+` only feature that will ideally support `if-else`

would printing all attributes be prohibitive?