Improve `modulesIntegration` for ESM

[lforst]

Description

Currently the modulesIntegration does not work for ESM. Maybe we can use import-in-the-middle to improve that situation.

[dumbbellcode]

hey @lforst, i was thinking about working on this, so i started to look into the code for modulesIntegration and realised it doesn't really capture information about most of the installed packages, the reason being sentry (for Node) is initialized at the beginning of the app (using instrument.ts), so it is only able to capture information about packages available in require.cache at that time. Let me know if it makes sense.

[lforst]

@dumbbellcode Yup that's totally possible. Historically we have neglected this integration a bit because it doesn't provide too much value to Sentry users directly. However, it can be immensely helpful to us when we help troubleshoot issues with the SDK.

[dumbbellcode]

which means there are 2 distinct issues to work on,

1. Fix the current integration so that it captures information about all packges (might degrade performance slightly)
2. Add ESM support to the integration

I am planning to work on both but I think it's important to fix the 1st issue itself as it makes the integration obsolete if not fixed, could you create an issue and assign it to me ?, i'll give it a shot. Thanks !

ping: @lforst

[lforst]

@dumbbellcode feel free to just submit a PR outlining the problem and how you're solving it. Thanks!

[dumbbellcode]

sure @lforst, will create an issue and submit a PR in some time 👍