Kevin McGonigle

In a similar situation where I'm trying to ensure the _abscence_ of a certain header, rather than its presence - not seeing a nice way to go about it.

Hey @vamshich13, have you tried running unit tests in jest or vitest where members of this package are imported? It gives rise to some pretty gnarly errors. I'm in touch...

Hi @xerxovksi, just tried that out for both jest and vitest and experienced the same behaviour as before for both.

As suggested by @Qard [here](https://github.com/DataDog/dd-trace-js/issues/3524#issuecomment-1734324979), one possible solution might be using the loader hook provided by dd-trace to support ESM: `node --loader dd-trace/loader-hook.mjs your-app.js`. I have, however, found that the...

A workaround I've just found to have the resource names set correctly is to set it via the http plugin: ```ts export async function register(): Promise { if (process.env.NEXT_RUNTIME ===...

> If so, you will need to use the loader hook. node --loader dd-trace/loader-hook.mjs your-app.js @Qard I'm not sure that's trivial/possible with Next.js. In my case, using the app router,...

> https://caniuse.com/mdn-api_textencoder > > This API has been available in browsers for a long time, added in Chrome 38 which was published on 15th of August 2014. Looking at the...

@MenaiAla If most of your tests are for code executed in the node runtime, then going the opposite direction of setting the `testEnvironment` property of your jest config to `'node'`...