try using playwright instead of puppeteer. puppeteer can not provide raw v8 coverage data, or using puppeteer-to-istanbul

• playwright -> v8-to-istanbul
• puppeteer -> puppeteer-to-istanbul

Thanks for the tip! Are you sure about puppeteer not providing raw coverage? As the method name that I linked to my code is a new edition in v8 that output raw coverage as far as I understand, but I don't understand much...
https://github.com/maplibre/maplibre-gl-js/blob/f197991152117c6e3964f824ebb6e3cec7d2d218/test/integration/render/run_render_tests.ts#L795C51-L795C51

Yes, puppeteer can provide raw v8 coverage data with option includeRawScriptCoverage
Is it still not working?

It works, but it doesn't work well, it reports comments and empty lines as not covered.

There should be a bug somewhere, it could possibly be a problem with the sourcemap, see this issue, but it seems to be hard to fix. Therefore, we have implemented our own coverage report, see here.
see codecov example: https://app.codecov.io/gh/cenfun/playwright-ct-vue/blob/main/src%2FApp.vue
The comment lines and blank lines will be ignored.

Thanks, I guessed the same regarding sourcemap or conversion issue.
I'll check your links, thanks!

@cenfun if you want to open an issue on this repository, I'm open to moving towards retiring the guts of v8-to-istanbul in favour of your implementation, if we can show:

• It works with all existing test cases (both for v8-to-istanbul and c8).
• It works on large codebases like Node.js.
• It uses a reasonable set of dependencies.

I'm worried the AST might fail in certain edge-cases, but open to this as being a good potential solution.

@bcoe Thanks for your suggestion. My implementation simply provides a custom coverage report for Playwright, and we don't want to use Istanbul to instrument the source code because it's very slow, V8 is faster.
But I never intended to replace tool v8-to-istanbul, because they have different functions. My implementation is more about displaying the native V8 report directly.

• Bytes coverage
• CSS Coverage

There is gist here: https://gist.github.com/cenfun/0754c23f03d1aa541b4467920ab4d09f

Would it work if lines that are not present in source maps would be excluded from the report? There would be no need for AST.

There's related PR in #240 but that one attempts to detect lines using regexp.

@AriPerkkio Just sharing my experience how to exclude blank lines and comment lines.

• line-parser.js Detecting blank lines
  • comment-parser.js Detecting comments for line parser

BTW, the problem can't be solved by using regular expressions. see example if the comment is inside a string. That's why I implemented comment-parser.js It seems to work very well.

• line-parser.js Detecting blank lines

  • comment-parser.js Detecting comments for line parser

These implement comment detection by parsing the content characted-by-character? Handling all weird edge cases that JS syntax allows might be difficult.

Here is another attempt based on the idea from #238 (comment) - ignore all lines that are not present in source maps. Left side is before, right one is after:

This is all done in ~13 lines of code using @jridgewell/trace-mapping which is already a dependency of v8-to-istanbul. No need for AST or parsing the source file for whitespace.