We’re loading the Sentry Browser SDK from the CDN and calling
Sentry.init() to configure it. We would like for errors to not be logged until we call
Sentry.init(). Ideally errors caught before
Sentry.init() would be queued so that they could be run through our custom
Are errors supposed to be logged before
Sentry.init() is called? Is there any way to stop it?
Sentry.init() a little late because we want to filter out errors from old browsers. Our site has a rather strict set of supported browsers. We have logic client-side to detect whether a browser is supported, and we’d like to call that from
beforeSend but the logic is in a file that’s loaded async so we need to wait for that file to load. Hence it’d be ideal of errors caught before
Sentry.init() were queued and would be run through our custom
beforeSend filter when it’s ready.