With the latest release there has been an increase in errors being captured that were not suppose to be (mostly anything that used the error system to log or produce a window warning).
This PR switches these warnings to be produced at the code flow spot that the issue occurs rather then bubbling the warning up through the new Error functionality and eventually into the sentry exception handler.
This should have no effect on the end user and will massively reduce the number of events going to sentry (we only want to know about issues in the extension not peoples specific usage).
Changes
[x] use sentry browser to have more control over exceptions and release health
[x] remove usages of piggy backing on error bubbling for warnings
[x] fix failing build due to old typescript version
Description
With the latest release there has been an increase in errors being captured that were not suppose to be (mostly anything that used the error system to log or produce a window warning).
This PR switches these warnings to be produced at the code flow spot that the issue occurs rather then bubbling the warning up through the
new Errorfunctionality and eventually into the sentry exception handler.This should have no effect on the end user and will massively reduce the number of events going to sentry (we only want to know about issues in the extension not peoples specific usage).
Changes