Gerhard Stöbich

> This is a hack that gets the tests passing locally: I think before doing that we should move away from using require-in-the-middle or request an API for thins via...

I guess such problems are not limited to `SpanProcessor`. Any exported class may result in similar problems. see the recent [issue](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/983) for contrib instrumentations. I guess to fully avoid this...

I'm fine with rename metrics. I'm not really a fan of the term SDK in this context but I guess this is because the name was given by the spec....

Still keep three packages (node + web + common/base/shared/...). If someone uses only base then fine - it contains code working on all platforms and user has a single entry...

> I don't see any reason to use `NodeTracerProvider` over `BasicTracerProvider`. I think the only good reason to use it is it takes care of creating, enabling and installing `AsyncLocalStorageContextManager`...

Please provide a reproducer showing how you setup otel and how you set the span as active on context. Does `trace.getSpan(context.active())` work for you e.g. withing an incoming HTTP request...

The corresponding issue in node repo: https://github.com/nodejs/node/issues/42237

Setup/configuration of collector is not JS specific and should be most likely discussed in the collector repository. Regarding SDK setup there is no new/old way. * Using (still experimental) `NodeSDK`...

There is no new and old way. There are different ways and you have to choose one depending on what you would like to archive. I agree that documentation is...

Yes, for trace you can use `NodeTracerProvider` or `NodeSdk`. `NodeSdk` uses `NodeTracerProvider` internally - it's just a higher level entry point which covers more then tracing. In browser the entry...