Repository navigation
Allow capturing exceptions without having to override window.onerror #91
Description
Currently Raven.captureException does not work unless .install() has been called, but calling .install() replaces window.onerror to sending every error to Sentry (we are seeing a lot of errors that are not from our web app, appear to be content scripts, other scripts injected onto the page by browser extensions etc.)
Raven.captureMessage seems to work fine without the need to call .install()
Activity
mattrobenolt commentedon Mar 27, 2013
@ram-nadella I agree, and I'm currently working on a small project that is (hopefully) going to be able to replace the underlying library I am using in raven-js. This new library won't require patching window.onerror when loaded on the page. :)
So consider this a WIP.
ram-nadella commentedon Mar 28, 2013
Nice.
Thanks for the update. Any ETA? Happy to contribute if necessary.
mattrobenolt commentedon Mar 28, 2013
Not at this time. Give me a week or so, and things should be in a usable state. I'm pretty excited about it.
dknecht commentedon Apr 11, 2013
HI Matt- How is this going? We would be interested in testing.
ryanwitt commentedon Apr 11, 2013
+1
mattrobenolt commentedon Jan 19, 2014
Just do:
costa commentedon May 15, 2016
@mattrobenolt I hope you're still the maintainer. Hi, may I use the aforementioned option in production? I mean, two years have passed and it didn't make into the config docs, I wonder why.
While on the subject, I'm trying to make use of Sentry for a client-side plugin which means I do not own the page I'm collecting errors from. Now as far as I can see
Raven.noConflictdoesn't exactly cover for multiple Sentry apps on the same page — and I have to use the (undocumented) option above. Is there anything else — in your opinion — I should be aware about? Thank you very much.jsyrjala commentedon Sep 22, 2017
@costa Documentation for the
collectWindowErrorsoption got added in this pull request #1050