missing error.code on uncaught exceptions

[kkmuffme]

Important Details

How are you running Sentry?
sentry.io

Description

Not sure if this is a bug, an oversight or a feature request, but:
when sentry catches uncaught exceptions (e.g. onunhandledrejection), it reports only the error.message
This error message often times is pretty useless, especially when it comes to browser specific error messages (e.g. localStorage issues,...).

Possible Solution

Reporting the error.code, which is consistent between (most) browsers in addition to the message would be a lot more useful.

[BYK]

Closing this issue due to staleness. Feel free to comment here if you think we should still work on this.

[kkmuffme]

Bump

[BYK]

Alright, transferring to sentry-javascript repo where this should be addressed in.

[lobsterkatie]

@kkmuffme - Can you try using the ExtraErrorData integration documented here? That should capture any non-standard properties on the error object.

(We only grab the standard properties by default.)

[kkmuffme]

@lobsterkatie unfortunately all of these errors (onunhandledrejection) are so exotic, I was never able to reproduce any of them myself.

Anyway: the error code is a standard property, isn't it? https://developer.mozilla.org/en-US/docs/Web/API/DOMException
Even though .code is there for legacy reasons, at least the "new" .name should be supported by default.

[lobsterkatie]

Ah, right, DOMExceptions. We do grab the .name property (which you can see here) but you're right that we don't grab the .code property. That said, seeing as it appears to have been deprecated 9 years ago in favor of .name, that feels like a fair omission.

[kkmuffme]

It is deprecated, unfortunately it is widely used still and often makes more sense than .name as browser seem to set all kinds of unstandardized things there, but use consistent .code values

[lobsterkatie]

Okay - I'm adding it as an event tag: #3018.