Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Typescript coverage doesn't include some lines after 13.2.0 update
See original GitHub issueLink to bug demonstration repository.
https://github.com/damyanpetev/typescript-coverage-repro
(install nyc@latest to see the difference)
Expected Behavior
Coverage report on a TypeScript project to include all relevant lines and if/else paths.
Observed Behavior
After updating v13.1.0 to latest (specifically above v13.2.0) coverage percents differ and seem to ignore some lines (specifically noticed that with if/else blocks). Consequently, the coverage also doesn’t report the if/else paths that are not taken:
Forensic Information
Operating System: Windows 10 Environment Information: tested on both node v8.15.1/v10.15.2 with npm 6.4.1. (initial commit on demo repo has package-lock.json with packages installed)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can’t say for the original report, but my problem is gone with nyc@14.1.0. Thanks!
@damyanpetev @fictitious please retest with nyc@14.1.0 (currently published to npm
nexttag). This should resolve the issue for you.