-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng test: Source maps don't match when using --code-coverage #19084
Comments
Hi @daelmaak, Had a quick look at this and from my initial investigation this looks more of an upstream issue. Likely, it's in https://github.com/JS-DevTools/coverage-istanbul-loader or https://github.com/istanbuljs/istanbuljs |
This appears to be the same as #7117. The discussion there indicates the issue is with webpack-contrib/istanbul-instrumenter-loader. Regardless, this makes debugging Angular tests, not even live debugging but just referencing line numbers in test output, impossible when code coverage is enabled, which Angular does by default. Caveat: I'm currently still using Angular 8, though apparently the issue is still outstanding. |
I'm sorry, but this issue is not caused by Angular CLI. Please contact the author(s) of the @jsdevtools/coverage-istanbul-loader project or file an issue on their issue tracker. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Not sure.
Description
When running
ng test --code-coverage
and then debugging in chrome, the source maps don't match the actual code. On picture, the execution should have stopped atdebugger;
, which it seemingly doesn't:🔬 Minimal Reproduction
Using ng cli 10.1.5
ng test --code-coverage
🔥 Exception or Error
none
🌍 Your Environment
Anything else relevant?
not to my knowledge
The text was updated successfully, but these errors were encountered: