6.56 MB install size

c8 has a huge 6.56 MB install size:

https://packagephobia.now.sh/result?p=c8

With 97 modules in the dependency graph:

https://npm.anvaka.com/#!/view/2d/c8

It is surprising how heavy this package is, considering v8 does all the heaving lifting and it mostly just needs to display a report. Is this something that can be improved upon, are there low hanging fruit?

handlebars (4.42 MB) jumps out.

From a complexity perspective, could the v8 coverage data could be reported directly, without a conversion process to the instanbul format?

[SimenB]

Handlebars has been removed from beta version of istanbul, which was upgraded in #168. You’re waiting for #170

[bcoe]

@jaydenseric 👍

I tried for about 3 days to do my own merging of V8 code coverage data from multiple processes, but found many bugs and mysteries (very little docs) around what exactly makes

Yes, my first implementation of this was terrible and Node.js’ merging process, which involved merging 1000s of reports took 30 minutes. @demurgos did an incredible job with this algorithm.

It only has around 240 source lines of code, so the vast majority of the install size comes from the @bcoe/v8-coverage dependency, which unfortunately has a 271 kB install size:

Mind listing the install size of c8@next, and potentially nyc@next on your package’s README?

https://packagephobia.now.sh/result?p=c8@7.0.0-candidate.0

As @SimenB mentions, a good chunk of the install size is handlebars, so the packages are a bit smaller than you draw attention to.

I’ll have next moved to latest midway through this week.

Very sad that V8 coverage data is really only reliable enough to use from Node.js v13.3+

I’m glad to have another person debugging V8 and filing issues. I’m actually feeling fairly positive, because it’s taken two years to get to the point where V8’s coverage is comprehensive enough to consider.