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

Source Maps #61

Closed
deckar01 opened this issue Feb 9, 2017 · 2 comments
Closed

Source Maps #61

deckar01 opened this issue Feb 9, 2017 · 2 comments

Comments

@deckar01
Copy link

deckar01 commented Feb 9, 2017

I am doing a lot of debugging in the HTML runner that jasmine generates, and am slowed down by the instrumentation injected into the source files.

I am planning to see if I can get a source mapped instrumenter working with this library.

The alternative is running the tests a second time with the coverage template turned off so that jasmine generates a runner with the original source files. That is not desirable, but maybe there is a simpler solution I am not thinking of.

@maenu
Copy link
Owner

maenu commented Mar 10, 2017

Running tests with uninstrumented code for debugging is what I did too in these situations.
Did you make any progress on this? Because it depends heavily on how istanbul instruments the sources. But it seems to be possible somehow, see this istanbul issue.

@deckar01
Copy link
Author

I did run across that issue, but that use case doesn't quite match up with mine. They were worried about getting 3rd party source maps into the reporter.

I just need istanbul to output a source map for it's instrumentation step.

I dug around a little, but I think it would require modifying istanbul's core instrumentation loop.

Closing for now.

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