-
Notifications
You must be signed in to change notification settings - Fork 136
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
Comments
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! |
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
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?
The text was updated successfully, but these errors were encountered: