You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
Along the lines of #288, this is a current shortcoming being addressed as part of work for #257. I didn't initially give enough consideration to what ideal behavior would be in the "development before production" use case.
For a workaround for now, you could listen to the logged event:
Raven.on('logged',function(err){console.log('raven reported an error:');console.error(err);});
or use the (currently undocumented) install callback argument:
Raven.config(...).install(function(sent,err){console.log('error caught by raven:');console.error(err);});
Consider the following snippet:
var Raven = require('raven'); Raven.config('https://abc@sentry.io/123').install(); throw new Error();
The thrown error is not printed to console.error; instead,
raven@1.1.2 alert: uncaughtException: abc123
is logged.During development, I (obviously) still need to see uncaught Exceptions for debugging.
I assume I misunderstood something, can someone point me in the right direction?
Thanks!
The text was updated successfully, but these errors were encountered: