TraceKit.computeStackTrace evaluates error to {}

[Myztiq]

I have created a reproduction hosted here: http://raven-undefined.divshot.io/
With source here: https://github.com/Myztiq/raven-undefined

A request to an invalid file triggers an error with the message Unexpected token < and when TraceKit.computeStackTrace is done it results in {} being spat out. This results in sentry getting errors with undefined as the value and message.

[Myztiq]

Should I instead file this ticket in the Tracekit repo? I realized that it's actually a standalone dependency moments after submitting.

[Myztiq]

Moved issue to TraceKit: occ/TraceKit#68

[mattrobenolt]

@Myztiq We maintain our own fork, and TraceKit upstream is unmaintained.

[niemyjski]

@mattrobenolt, @Myztiq, I'm helping maintain TraceKit upstream.. If you want to recreate all the issues / pull requests in the master I'll participate in the discussion and merge them in!

[mattrobenolt]

I'm going to assume this has been fixed since we've pulled in latest TraceKit recently.

[niemyjski]

If it's not let me know