Lukas Stracke

Hey @jdussouillez I'm aware of Angular's support policy, it's just that [our own support policy/philosophy](https://develop.sentry.dev/sdk/philosophy/#compatibility-is-king) is a little bit stricter. IOW we want to support old versions for as long...

Hi @throrin19 thanks for writing in! Sounds like we can't upgrade to the v3 SDK at the moment without dropping support for Node

According to the [v3 docs](https://github.com/aws/aws-sdk-js-v3#-nodejs-versions), Node 14 is the minimum. But according to @throrin19, > we have the problem of compatibility between aws node runtime < node18 using the sdk...

If anyone can provide a minimal reproduction (e.g. GH repo/stackblitz) we can debug this further. Thank you!

Hi @MSDev201 thanks for writing in! This is a somewhat known issue although we're not entirely sure what exactly is causing it. So far we've mostly pinned it down to...

> First of all, Im not sure if its correct to not await the flattening of the source maps. All processes are over when the flattening still is happening. oof...

@MSDev201 thanks a lot for investigating! To me, this looks like there's already a problem in the generated source map but sorcery also shouldn't cause an infinite loop because of...

Hey @MSDev201 thanks so much for investigating this further! So this is a really painful problem because I'm afraid, to fix this on our end, we'll somehow need to check...

Hi @Zih0 thanks for writing in and for opening the PR! Before we review and merge it, can you explain what the consequences of the SDK not setting this default...

Ahh I see, you're bringing up a good point. Let's try to align the behavior with the browser SDK. I just gave the PR a review. Looks good mostly, let's...