Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping of Typscript Source Files #142

Closed
dwgray opened this issue Sep 7, 2016 · 4 comments
Closed

Mapping of Typscript Source Files #142

dwgray opened this issue Sep 7, 2016 · 4 comments

Comments

@dwgray
Copy link

dwgray commented Sep 7, 2016

I'm using your instructions for debugging clicker app using npm run karma, choosing the debug tab in chrome, etc.

Everything works great, except that the application source files don't get mapped back to the original. I'm seeing something like the attached (which even though it says it's a .ts file and that chrome says that its mapping from the .browserfy file, it's obviously not the original source. Is this expected? If not, any thoughts on what might I be doing with the environment to lose the mapping? If so, how do you debug the actual app source?

app.ts.txt

Note that the .spec.ts files appear to be mapped. Is this some double compiler issue perhaps?

@lathonez
Copy link
Owner

lathonez commented Sep 7, 2016

see #119 and #121

I have noticed this myself, I think the transform crept back in to the debug run, possibly removed in #140

@lathonez
Copy link
Owner

lathonez commented Sep 7, 2016

This is working for me now:

screenshot-20160908093329-807x576

Though I think it's only since #140, so in 1.13.1. Do you have the fix in #140 / what version is in your package.json?

@dwgray
Copy link
Author

dwgray commented Sep 7, 2016

My apologies, I didn't sync before submitting this (in my defense, I had just pulled down the project yesterday). Works great with version 1.13.1. Thanks!

@dwgray dwgray closed this as completed Sep 7, 2016
@lathonez
Copy link
Owner

lathonez commented Sep 7, 2016

No worries, it's been broken for a while just a coincidence that it was fixed since you pulled in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants