Lukas Stracke

> we are unable to use the new `@sentry/google-cloud-serverless` library as our code is authored in ESM The code we ship in our `@sentry/google-cloud-serverless` package is CJS only at the...

Good idea! Would you be interested in opening a PR for this? No worries if not, I'll get to it next week.

@zip-fa I was thinking about the provider helper functions but any help is appreciated :) I wrote up an issue to track the provider functions in the SDK repo: https://github.com/getsentry/sentry-javascript/issues/9407.

Actually, that's a good point. Knowing which file in the route is responsible for the invocation would also be beneficial for Sentry as we could add this information to our...

I'd like to bump this as it's still important to us. However, I want to add another thing I recently learned: SvelteKit proxies or listens to accesses to various properties...

@benmccann thanks for the review and sorry for missing out on the code styling. I made an additional small change (see comment above). Lmk If I can do anything else...

Thanks for opening this PR @gtm-nayan! While @danieldiekmeier is right that this PR currently won't let us get rid of our flattening workaround with `sorcery`, #10069 would do that 😄...

Hi, Sentry dev 👋 I asked about this a while ago here along with some other source maps related stuff: https://github.com/sveltejs/kit/discussions/9608 We would really appreciate it if this was fixed....

> A fix could be to update the source maps while copying them. (But maybe there are better options.) I'm wondering if a simple option might be just changing the...

We would really appreciate it if this issue was bumped in priority. The current behaviour is blocking some of our users because our source maps flattening approach with `sorcery` fails...