Francesco Gringl-Novy

Hey, thanks for reporting this. We should ignore 4xx errors by default, you are right! We'll look into this. For now, you can filter them via the SDk, using beforeSend...

I looked over it again, apart from some rebase stuff that is sadly going to have to happen 😬 (e.g. the client type is now gone and just part of...

Looking great! Only things left IMHO: * move `getBodyString`, `FetchHint` & `XhrHint` to browser-utils * rebase and resolve conflicts

I can't push changes on your branch, so I opened a PR here: https://github.com/Zen-cronic/sentry-javascript/pull/1 which should fix the remaining CI issues on your branch!

Hey, thank you for raising this, and sorry this kind of fell of the radar. We'll try to update the docs to clarify this even outside of Next.js!

**Why was this issue closed?** This issue hasn't been touched recently and no longer seems relevant. Hence, we're closing it to maintain a clean and transparent backlog. Please feel free...

Would you be interested in seeing this updated to a current version (8)?

This is superseded by https://github.com/getsentry/sentry-javascript/pull/15542 - thank you for the effort on this!

Hey, this is a JS SDK issue, moving it to sentry-javascript!

If the content is bundled, they may need to configure things as external to work - instrumentation only works for external dependencies, not bundles one, as of now, sadly :/...