Skip to content

V8 coverage API next steps #35783

Closed as not planned
Closed as not planned
V8 coverage API next steps#35783
Assignees
joyeecheung
Labels
coverageIssues and PRs related to Node.js code coverage support.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@joyeecheung
joyeecheung
opened on Oct 23, 2020

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

Activity

  1. joyeecheung
    added
    coverageIssues 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-actions
    github-actionsbot
    on Jun 27, 2026 – with GitHub Actions
    Contributor

    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.
    on Jun 27, 2026

  5. github-actions commented on Jul 28, 2026

    @github-actions
    github-actionsbot
    on Jul 28, 2026 – with GitHub Actions
    Contributor

    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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coverageIssues and PRs related to Node.js code coverage support.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions