useSentry: Option to exclude errors from reporting

[dburles]

Feature request

There's no way to exclude errors from being reported. Ideally there could be a configuration filter option to opt-out.

Something like:

useSentry({
  skipError(error) { return error instanceof MyCustomError; }
});

I'd suggest renaming skip to skipOperation if we go with skipError.

Bundling bug

I tried to extend my custom errors from EnvelopError as a workaround, though I was stumped as to why this didn't work until I realised for some reason it's actually being bundled into the Sentry plugin, https://unpkg.com/browse/@envelop/sentry@1.3.0/index.mjs so fails the instanceof check, when imported from @envelop/core.

[saihaj]

If you throw EnvelopError they are excluded from error reporting #855

[dburles]

That's what I was doing essentially, but it fails the instanceof check as it's not the same class as in core.

[n1ru4l]

@dburles Can you create a minimal reproduction of this?

[dburles]

This issue has kind of become two, a bug report for the bundled EnvelopError class and a feature request for a configuration option to skip errors, the latter is the part I am interested in. I would love to help and create a repro for the instanceof issue, but I cannot devote the time to it at the minute. I believe the problem is clear in any case and that it is solved by not bundling mono repo dependencies.

[n1ru4l]

@dburles This will be taken care of by #936. I will let you know once it is merged and released!

[dotansimha]

@dburles This will be taken care of by #936. I will let you know once it is merged and released!

@dburles anything needs to be done on this PR? I think the changes Laurin mentioned are already in.

[dotansimha]

Available in @envelop/sentry@1.5.0 :)