Roch Devost

This was removed because of issues with the previous plugin system which has since been replaced. It should be possible to restore this feature at this point. I'll have to...

@clement-heliot Thanks for the additional context in #2225. It wasn't clear to me what the use case was for this was, although it seems pretty clear now that it's basically...

When you say "stop reporting" do you mean that you're no longer getting traces at all, only when you use a blocklist configuration?

Is this something you are able to easily isolate in a reproduction snippet? Also, was there anything else in that change, for example changing the version of dd-trace?

Right now we only support libraries that are not included in the bundle, so the ones marked as external as you mentioned above. We will eventually work on improving our...

In the above example, the object is stringified before being sent to the logger. The tracer needs an actual object to be able to do the injection, since a string...

@joshribakoff-sm The main thing that usually breaks things is load order issues since dd-trace needs to be the very first thing loaded _and_ initialized before anything else is imported. When...

> There must be more to it than this. When importing dd-trace first, or turning on automatic integration at all, too much stuff breaks. For example, our logger uses one...

Looking at the [nightly test](https://app.circleci.com/pipelines/github/DataDog/dd-trace-js/6919/workflows/9f1186dd-4c6e-489f-9725-fac6e5080b3b/jobs/864725) it looks like our tests are passing for `4.5.0`. Can you share a reproduction snippet?

Can you share runnable code that reproduces the issue? On my end everything works as it should.