Coverage information in dist/main.js
See original GitHub issueHey,
I upgraded to react-json-view@1.20.2 and for some reason, jest’s coverage check started failing. After some debugging I found out that the dist/main.js
file from react-json-view
has something that resembles coverage information 🤯
I reckon it would be best if the coverage information was not included 🙂 I tried to take a look at the repo configuration but I did not find anything that would indicate invalid config.
Thanks for maintaining the library, by the way!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
JavaScript code coverage · V8
Code coverage provides information about whether, and optionally how often certain parts of an application have been executed.
Read more >Code coverage from Nightmare.js tests - atodorov.org
In this article I'm going to walk you through the steps required to collect code coverage when running an end-to-end test suite against...
Read more >Setup TypeScript code coverage for Electron applications
Node.js v10.9.0; Electron v4.0.5. To receive code coverage based on TypeScript source code within an Electron environment, we need to do the following:....
Read more >How to enable Istanbul code coverage for the mocha plugin?
I don't know it is an expected answer, but it worked for me by following that mocha-webpack guide and adding the loader to...
Read more >Not getting code coverage information - Stack Overflow
I'm running a Unit test experiment on our existing Webapp folder structure. When I run the tests on an AMD and non-AMD js...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
haha fuck!
thanks for pointing this out. There were some massive dependency updates between 1.19.x and 1.20.2.
I’ll be working on damage control tomorrow to address issues coming from those changes.
this looks like an obvious screw up on my end… i clearly included coverage info with the assets published to npm.
I should have this resolved some time tomorrow. I’ll post an update when the update is being published.
thanks again for posting extra detail @Gelio !
MR #318 will resolve this issue. i had babel including the
istanbul
plugin for all environments. the fix also cuts the build size in half.once the MR is merged, i’ll publish to npm at
1.20.3