Show typescript sources in chrome devtools stacktrace about augury

[alexeagle]

Can post a minimal repro if that's helpful.

[bertrandk]

From what I can tell, this is an issue with Chrome.

It may be worth looking into https://github.com/stacktracejs/stacktrace-gps or https://github.com/novocaine/sourcemapped-stacktrace when we take a stab at error notification in the extension.

/cc @winkerVSbecks

[igor-ka]

Thank you for your feedback @alexeagle

Sourcemaps in chrome extension seems to be as easy as everywhere else. There is a PR, I misread the original issue earlier, so I will keep this open.

[winkerVSbecks]

With the new Webpack build system we have source-maps generating. I just need to link it to the file or make it inline.

[alexeagle]

We were able to generate sourcemaps with webpack - as I said, we can set
breakpoints in TypeScript files. The issue is just with presentation of the
stack trace.

On Wed, Oct 28, 2015 at 4:53 PM Varun Vachhar [email protected]
wrote:

With the new Webpack build system we have source-maps generating. I just
need to link it to the file or make it inline.

—
Reply to this email directly or view it on GitHub
#34 (comment).

[winkerVSbecks]

@alexeagle I merged PR with the Webpack build like an hour ago. Just tested break-points and console.logs. There are 2 levels to this:

1. Devtools where Batarangle is running
2. Devtools to debug Batarangle itself

In (1) the logs are linked to the .ts files. In (2) the logs don't seem to be linked to .ts files but, the break-points are.

Can you confirm that?

EDIT: And this is what I get for stack trace in (2)

[alexeagle]

great, that looks good from the screenshot. I don't have time to fetch the latest and verify right now, am working on other stuff. Thanks!