Jonas

@andreiborza @Xhale1 are you seeing any profiling SDK logs if you set debug: true to the SDK init?

@Xhale1 are you setting profilesSampleRate as well, or is that not defined? I can see the SDK enables continuous profiling mode, which should only be enabled if profilesSampleRate and profilesSampler...

Let me look at the repo. If you setProfilesSampleRate, then the continuous profiling log should not appear, if it does, then that is an SDK bug. I'm going to investigate

Ok, so if I set profilesSampleRate to > 0 and curl the endpoint (curl localhost:3000), I can see that the profiler is started and stopped. ``` // instrument.ts Sentry.init({ dsn:...

@Xhale1 That seems to be the case yes. I dont know exactly what the check relies on, maybe its, because there are no routes defined in the file?

@Xhale1 I doubt that node profiling is the issue here tbh, are there any other differences? I can see from the example you shared above that the the successfully instrumented...

@andreiborza @Xhale1 unfortunately yes, and I dont think there is much we can do about it right now. The reason why profiling uses require (via createRequire) in ESm is because...

@Xhale1 afaik there is nothing wrong with using ESM and createRequire like we do here, meaning your program should still run in ESM, except when it comes to requiring the...

> Thank you for the details! I appreciate you're time here and you looking into improving that debug message for better clarity. I think the only the only remaining mystery...

Hey everyone, I've made a change to scope require creation to the binding import [here](https://github.com/getsentry/sentry-javascript/pull/13834) so that we dont end up tripping cjs detection.