Tim Fish

Ah, another issue here is that `module_metadata` is `any`. Users could set this to a `string` via the bundler plugins and then we can't include our key with any existing...

I can't reproduce any build or runtime errors with any v8 SDK version: `package.json` ```json { "scripts": { "build": "pkg -t node18 index.js" }, "dependencies": { "@sentry/node": "^8.5.0", "pkg": "^5.8.1"...

The above PRs have been merged and we're just waiting for these changes to make it through all the required release processes. Until then I've made a patch which can...

Hi @MeCapron, This looks like a different issue and is very strange since all this code is CommonJs! Could you open a new issue with a minimal reproduction so I...

It looks like `openai/resources/index.mjs` exports two different `Completions` classes, one for `/completions` and one for `/chat/completions`. For `import-in-the-middle` we deduced that for ESM, duplicate named exports were not exported at...

I've opened a PR for `import-in-the-middle` to fix this: https://github.com/DataDog/import-in-the-middle/pull/103

This should hopefully have been fixed by the numerous PRs recently merged at `import-in-the-middle`. While we wait for this to be released, there is [a patch available](https://github.com/getsentry/sentry-javascript/issues/12485#issuecomment-2169398097) that combines all...

There has been some remaining issues reported with `openai` due to the way it's "shims" work internally. For example, someone has reported issues with this code: ```ts import OpenAI from...

The next SDK release will have a way to work around this issue.

With v8.18.0 of the SDK just released, there's a new config option which can disable `import-in-the-middle` for specific libraries: ```ts import * as Sentry from '@sentry/node'; Sentry.init({ dsn: '__DSN__', registerEsmLoaderHooks:...