sentry-javascript

No need to clutter your code with a bunch of try wrappers like this suggests. There's a much better way. It turns out that in a typical web app, a handful of operations account for the vast majority of new execution contexts: - setTimeout/setInterval - event handlers - ajax response handlers Wrap those entry points (along with a single top-level wrapper which can be done as a build step) and you're almost entirely covered. If you use jQuery along with TraceKit, this plugin does it for you: https://github.com/getsentry/raven-js/blob/master/plugins/jq...

If using jQuery, it is a few lines of code to add try/catch around the majority of your code entry points. Go to https://github.com/getsentry/raven-js/blob/master/dist/1.0.8... and you will see code that wraps $.event.add(), $.fn.ready(), $.ajax(), window.setTimeout() and window.setInterval() (search _helper).

Go to https://github.com/getsentry/raven-js/blob/master/dist/1.0.8... and search for jQuery. You will see code that wraps $.event.add(), $.fn.ready(), and $.ajax() Search for _helper('setTimeout') and _helper('setInterval') to see how it injects exception capture for those functions. The above cover the vast majority of code entry points if using jQuery.

So somehow I've never noticed this as a problem. We get full stack traces for everything. On the other hand we use the hosted version of Sentry (https://getsentry.com), but since everything is open source, we bundle their raven library (https://github.com/getsentry/raven-js) into our CDN served package. So window.onerror is set from the same JS as the rest of the app. I'm guessing that avoids the cross-domain issue?

Here you can find the open sourced JavaScript lib https://github.com/getsentry/raven-js