Disable for development

I’m having trouble figuring out how to restore the window.onerror event after including Raven as an AMD dependancy.

I don’t want to use Raven at all during development, so I’m only calling config()/install() in production mode. But in dev mode all errors are still being thrown by TraceKit.report()… Which is pretty frustrating since the file/line number/stack trace isn’t helpful anymore in the browser dev tools.

I’ve tried calling uninstall() in dev mode but that didn’t help. Is there a reason you’re binding to window.onerror no matter what instead of doing it inside config() or install()?

[paulredmond]

For those coming here trying to figure it out still, it was a config option I missed at first shouldSendCallback:

import Raven from 'raven-js';

const env = 'prod';
const release = '12345';

Raven
  .config('https://<example>@sentry.io/1234', {
    environment: env,
    release: release,
    shouldSendCallback: () => {
      // Do your logic here...
      return ['prod', 'staging'].indexOf(env) !== -1;
    },
  })
  .install();

If shouldSendCallback is false sentry will not report. No need for conditional reporting logic in your code with this 👍 .

[paragjnath]

I have used this way. It seems working for me

if (environment.production) { Raven.config('https://@sentry.io/') .install(); }

and in providers providers: [environment.production ? { provide: ErrorHandler, useClass: RavenErrorHandler } : [], ...

Please let me know if I am doing anything wrong here.