@eriwen eriwen released this Jun 13, 2016 · 12 commits to master since this release

Synchronous Stack Traces

Due to popular demand, we've provided a synchronous way to get stack traces.


HEADS UP: Does not enhance stack traces with source maps or guess anonymous functions like StackTrace.get() does.



@eriwen eriwen released this May 28, 2016 · 21 commits to master since this release

Error Messages in Reports

StackTrace.report() now accepts an optional message

var stackframes = [StackFrame(...), StackFrame(...)]
var url = 'https://reporting.yourservice.com/jserror'
var message = 'undefined is not an Object'

StackTrace.report(stackframes, url, message)

Example JSON POSTed:

  message: 'undefined is not an Object',
  stack: [
    {functionName: 'fn', fileName: 'file.js', lineNumber: 32, columnNumber: 1},
    {functionName: 'fn2', fileName: 'file.js', lineNumber: 543, columnNumber: 32}



@eriwen eriwen released this Apr 1, 2016 · 76 commits to master since this release

Better parsing

Updated error-stack-parser to v1.3 which parses eval stack entries in a better way and fixes a bunch of bugs.

Better resource handling

Updated stacktrace-gps. Now reuses the same instance to avoid duplicate requests for the same resource by default.

Better dev experience

JSCS and automated PR testing have been implemented to ensure consistent styles and quick feedback.

Possibly breaking changes: ErrorStackParser now provides it's own polyfill for Array.map and Array.filter. eval information is will display differently in stack traces.