Weyert de Boer

Are there any decisions made on the OM text format? I would interested in implementing the text format for the OpenTelemetry Prometheus exporter in `otel-js`.

If I understand it correctly the extension has a hard-requirement that you install `vitest` in the root workspace otherwise it is not working. I think it would be nice if...

Anyone found a solution for this?

I didn’t know you could destruct class instance like this 🤔

I have tried it out but I have occasions were the arguments is `[fn, undefined, undefined]` and then the `arguments.length` fails. I think we might want to do something like...

@secustor Sorry for being unclear I was referring to the `massageParams` function. Also any particular reason why it's not part of the class itself?

> > Another option to avoid the need for monkey patching / loader hooks would be to avoid creating speparate instrumentation packages. > > Instead integrate OpenTelementry API directly into...

My understanding is that diagnostic_channel would be the right way to approach this but then you still have the chicken-egg problem as the package needs to instrument

I am wondering what's easier to convince package maintainers to instrument with `diagnostic_channel` or `@opentelemetry/api`. Personally, would prefer the latter :D

Is this normal behaviour of Github Actions? If not, I think it's better to use some special named `.env` for `act` to avoid unexpected behaviour when writing workflows.