Marc Pichler

Hmm, I did some (light) digging but could not find a reason as to why this MUST requirement is there. As you mentioned in > It isn't clear to me...

Hi @ruslan-mikhailov, thanks for reaching out. Yep, that's quite annoying behavior. When I restructured the exporters I decided to keep it as-is I wanted the restructuring to feel as close...

(such a change would affect all grpc exporters, metrics/traces/logs alike, as they all suffer from the same issue)

Closing this one as it has a few conflicts. If anyone's interested in getting these changes in, please feel free to open a new PR. Thanks! :)

Thanks for looking into that. > Presumably we should drop the current node14 and node16 compat versions (our base Node.js is v18 now) and add node18 and node20 compat versions?...

I think we can spin off `good-first-issue`s to remove these packages and add a lint step for `@types/node` to be pinned, and close this issue. WDYT @trentm? 🙂

(we actually removed them a while ago so this issue is done)

Hi @vitorvasc, we've just merged the PR that adds the option to opt-out #4617, I think that should meet your requirements. I'll be included in the next feature release. 🙂...

I'm also happy to help out with this one. :slightly_smiling_face:

I also support Option 3. ~~One question: If we want to double emit with Option 3 we would tell people to install the old version via `npm:@`, correct?~~ (Edit: nevermind,...