Luca Forstner

Closing because at the time of writing this, the issue is unfortunately unactionable.

@iacobus Thanks for the patience! Very cool that you got the integration working yourself. The likely reason you're not getting any data in the queues module yet is that the...

As far as I can tell we are also adhering to the otel sem conventions except for the span op - which is not an otel concept.

@haseeb-numu In case pm2 messes with `Error.stack` in any way, source mapping with Sentry will not work. The SDK relies on the stack trace to be correct and original. If...

@haseeb-numu Not really no. Messing with `Error.stack` is bound to run into problems because it alters native behaviour that other tools like Sentry depend on. I think it is better...

I haven't tried it myself tbh but I'd assume that you would just have to add the webpack plugin here: https://rspack.dev/guide/migration/webpack#community-plugins What exactly isn't working?

@captain-hak would you mind sharing a reproduction example with the error? I just tried out the Sentry middleware with trpc@11 and I don't get any type errors.

@Lms24 I think this is more about the situation where a yarn.lock and a package-lock.json or equivalent are present. I don't think we should add a package manager command line...

@Bruno-DaSilva your assumption is correct in that the integration immediately continues execution when a breakpoint is hit. - [x] First thing we should definitely do is adjust the docs to...

I wonder if we could listen for new sessions to connect in any way and then dynamically disable the integration. :thinking: