fix(sveltekit): Avoid capturing redirect()
calls as errors in Cloudflare
#16853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on top of #16852 to avoid capturing errors too early and too generally via the
initCloudflareSentryHandle
request handler. Internally, this handler used a wrapper from@sentry/cloudflare
to capture errors but prior to #16852 it captured everything that was thrown. This included thrownredirect()
objects from SvelteKit which serve as control flow mechanisms but should not be captured as errors.This PR opts out of capturing errors in the Cloudflare wrapper. Instead, we rely on our already existing error capturing mechanisms in SvelteKit, which already ignore
redirect()
and a few other error classes.closes #16847