Roch Devost

We have re-written the plugin system and in some cases it's more prone to issues when the tracer is not initialized in the right location, at least right now. Can...

@mariuszbeltowski Yes but it's extremely verbose, so it's recommended to enable it only to debug issues. This can be configured with `DD_TRACE_DEBUG=true`.

@alvarofpp Were you able to solve the original issue? If not, can you try with 2.13.0? We made further changes to the plugin system that could hopefully fix the issue....

> It seems to be working fine now, but do you think it's possible that I may have issues again with future versions of the library? @dyarleniber We plan to...

There are a lot of Node built-in modules that are not available, which shouldn't be possible in Node. Is this a browser build? If that's the case, browsers are not...

Yes, it should be restricted to the server. Some versions used to "run" in the browser in the sense that it would transpile and not necessarily error, but they would...

It should be enough to tell the bundler that the dependency is external. I don't know how to do this with ESBuild but [this is how](https://webpack.js.org/configuration/externals/#externals) it would be done...

@sunsheeppoplar Unfortunately all planning is done internally and is not available publicly. We're not currently working on this but we still plan to work on it at some point. In...

A similar issue was recently fixed, so this might no longer be an issue in the latest version. Can you try upgrading dd-trace?

I couldn't reproduce using the above snippet, although I had to alter it quite a bit to make it run. I also wasn't able to reproduce the incorrect asynchronous context...