modulesIntegation throws error if used from ESM

[timfish]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

latest

Framework Version

No response

Link to Sentry event

No response

SDK Setup

modulesIntegration is excluded by default when using ESM but it can be added manually.

Steps to Reproduce

index.mjs

Sentry.init({
    dsn: '__DSN__',
    integrations: [
        Sentry.modulesIntegration(),
    ]
});

Expected Result

No error or at least an error that is more useful for debugging the issue.

Actual Result

This error in an endless loop:

ReferenceError: require is not defined
    at file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/core/esm/baseclient.js:632:15
    at Array.<anonymous> (file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:87:23)
    at file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:183:19
    at Array.forEach (<anonymous>)
    at SyncPromise._executeHandlers (file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:173:20)
    at SyncPromise._setResult (file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:161:10)
    at _reject (file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:144:10)
    at Array.<anonymous> (file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:84:13)
    at file:///Users/tim/Documents/Repositories/repro/node_modules/@sentry/utils/esm/syncpromise.js:183:19
    at Array.forEach (<anonymous> 

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #14169, which was included in the 8.37.0 release.