Does not seem to work in ESM context

[danielberndt]

I didn't dig super deep into it, but after upgrading our fastify-based api server to ESM, this library stopped auto instrumentalizing all relevant services (fastify, http, https).

Is the instrumentalization architecture compatible with ESM?

Looking a bit into the code require.main does not seem to exist in ESM:

beeline-nodejs/lib/instrumentation.js

Line 123 in cdd32ad

let resolvedPath = require.resolve(m, { paths: require.main.paths });

TypeError: Cannot read properties of undefined (reading 'paths')

Having enabledInstrumentations: ["http", "https", "fastify"], in the setup config does not seem to have an effect either.

So I'm not 100% sure how ESM-compatible this library is.

[vreynolds]

Require in the middle magic is not compatible with ESM 😢 At this point, ESM support is most likely to come in OpenTelemetry (there's an ongoing effort).

This means we don't have a good answer for folks at this point in time. I expect we will see more people upgrade to modules as support matures across frameworks, so this is something we'll need to have an answer for soon.