TraceKit
TraceKit copied to clipboard
csnover
Attempts to create stack traces for unhandled JavaScript exceptions in all major browsers.
There are five flakey tests that have to do with ensuring the `window.onerror` is called and works properly. This needs to be mocked or figure out why the test occasionally...
I'm using mobx-state-tree, which generates very long error messages, when trying to instantiate a model with data that doesn't match the defined schema. It appends a full dump of the...
Hi, have made this change so, I only need to include TraceKit once on my frame page. Here is the code for the frame page. function insertTraceKit() { function yourLogger(errorReport)...
Line 1075 causes issues on our Safari instance when it cannot find the caller. As a result the computeStackTraceByWalkingCallerChain function returns with no message, even if a a valid stack...
Cloning over from https://github.com/occ/TraceKit/issues/61: --- Adding support for getting cleaner stack traces from minified JS files via source maps would be pretty amazing. Can leverage mozilla/source-map project for [decomposing sources...
I observed that while `error.name` is empty regularly, some browsers prepend it to the message. E.g. when having ``` js throw new DOMException("INDEX_SIZE_ERR"); ``` Those are the observed values: **Opera...
We should try and modularize the code base so the jquery/ajax and window.onerror logic is separated out. So if you're not using it, you're not paying the overhead cost.