Gerhard Stöbich

We patch/wrap just the exports and share this approach with other APMs and at least CLS like modules. But I think the loader hooks should be not limited to this...

One feature I miss in `AsyncLocalStorage` is to decide if context passing should happen or not based on the resource type. Technically it's correct to pass context via `setInterval` but...

For timers the timout would be helpful. some people use `setTimeout(0)` as replacement for `nextTick` which is interesting to track. But timers for minutes are usually not of interest for...

I'm also interested in getting an API regarding this. transformation plugins and APM tools currently monkey patch `Module.prototype.require`, `Module._load` or similar which is not that nice and will for sure...

I think one major point is also documentation: * I think it's needed to clearly specify which objects are passed as resource for the various async resource types - or...

Which API stability requirements do we have in node for deprecated and internal APIs? Experimental allows breaking changes even on patch releases. I guess this is not allowed for deprecated...

The root span may be on a different process which runs on a different machine. So really hard to get via OTel API. Even if the root span is in...

Have you verified that we can implement these APIs with the existing context managers (AsyncHooks, zone.js)? If not this would be quite problematic.

I think we should work on prototypes for async hooks and zone.js before adding this to API. Otherwise the risk is too high to loose support for a major part.

We could move API into core repo and link them via lerna :o). I think the development of such an API must start go hand in hand with core anyway...