Description

joyeecheung

opened on Oct 23, 2020

Issue body actions

Opening an issue to track the work before moving v8.startCoverage() and v8.stopCoverage() out of experiment. This will take some refactoring. See #33807 (comment) and #33807 (comment)

1. Add a v8.startCoverage() method to reuse the per-env connection, if NODE_V8_COVERAGE is not set (would be useful to restart after v8.stopCoverage())
2. It would be good to have an API that (optionally?) returns the coverage result. I think it should be v8.takeCoverage() as the Profiler.stopPreciseCoverage command doesn't return this but the Profiler.takePreciseCoverage does. Also, I realize that this method should be asynchronous as there's no guarantee that we can get the response from inspector synchronously (it just happens to be this way right now), so it should probably return a promise.
3. Error reporting can be improved (return a rejection?)

Also #35212

Reacted by Simen Bekkhus and TZ | 天猪

Activity

1. joyeecheung

   added

   coverageIssues and PRs related to Node.js code coverage support.Issues and PRs related to Node.js code coverage support.

   on Oct 23, 2020
2. joyeecheung

   self-assigned this

   on Oct 23, 2020
3. github-actions commented on Jun 27, 2026

   

   github-actionsBot

   on Jun 27, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been marked as stale due to 210 days of inactivity.
   It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
4. github-actions

   added

   staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

   on Jun 27, 2026
5. github-actions commented on Jul 28, 2026

   

   github-actionsBot

   on Jul 28, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
   If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
6. github-actions

   closed this as not plannedon Jul 28, 2026

Issue actions