This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 135
Ability to see errors in console #259
Comments
@qrpike I'm not sure whether you're referring to uncaughtExceptions but you can use something like:
However this function only gets called when a ravenDsn is supplied. I have opened #283 to address that particular deficiency with this solution. |
My best workaround so far is to monkey patch raven method: function override(object, methodName, callback) {
// eslint-disable-next-line no-param-reassign
object[methodName] = callback(object[methodName])
}
// Monkey patch 🐒
override(raven, 'captureException', original => {
return (...args) => {
// Useful for debugging
if (process.env.NODE_ENV !== 'test') {
// eslint-disable-next-line no-console
console.warn('raven.captureException', ...args)
}
original.apply(raven, args)
}
}) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have Raven setup buy my biggest issue is when I'm developing locally I still want to see the messages in my console.
Adding:
Only shows me the event ID. How can I also console log the error. Maybe like:
Thanks,
The text was updated successfully, but these errors were encountered: