Hello,
I have ignore3rdPartyErrors enabled to reduce the noise from browser extensions, but it also prevents errors caught during the initial JS bundle loading to be ignored.
Before rg4js is loaded, it attaches a handler to window.onError, but it ignores every bit of useful information there only using the value of msg which is just a string that does not have any stack trace.
|
windw.onerror = function (msg, url, line, col, err) { |
|
if (originalOnError) { |
|
originalOnError(msg, url, line, col, err); |
|
} |
|
|
|
if (!err) { |
|
err = new Error(msg); |
|
} |
|
|
|
windw['rg4js'].q = windw['rg4js'].q || []; |
|
windw['rg4js'].q.push({e: err}); |
|
}; |
Because the error does not have stack trace, it gets ignored by ignore3rdPartyErrors.
Possible solution would be to extend that error with other data from onError like line number, filename etc and stop that error from being ignored by ignore3rdPartyErrors
Hello,
I have
ignore3rdPartyErrorsenabled to reduce the noise from browser extensions, but it also prevents errors caught during the initial JS bundle loading to be ignored.Before rg4js is loaded, it attaches a handler to
window.onError, but it ignores every bit of useful information there only using the value ofmsgwhich is just a string that does not have any stack trace.raygun4js/src/umd.intro.js
Lines 22 to 33 in a3f9b66
Because the error does not have stack trace, it gets ignored by
ignore3rdPartyErrors.Possible solution would be to extend that error with other data from
onErrorlike line number, filename etc and stop that error from being ignored byignore3rdPartyErrors