Coverage Engines: Bytecode Coverage via V8 AST Counters vs AST Instrumentation with Istanbul

Code coverage measures what percentage of your source code executes during a test run. Vitest supports two primary coverage engines: v8 and istanbul.

// vitest.config.ts coverage settings
export default defineConfig({
  test: {
    coverage: {
      provider: 'v8', // 'v8' | 'istanbul'
      reporter: ['text', 'json', 'html'],
      lines: 80,
      functions: 80,
      branches: 80,
      statements: 80,
    },
  },
});

V8 vs Istanbul Architectural Comparison

1. v8 (Native Node.js V8 Engine Coverage)

• Mechanism: Reads raw execution counters directly from V8’s internal bytecode inspector while running tests.
• Performance: Ultra-fast (~3-5x faster than Istanbul) because source code is not modified.
• Accuracy: Extremely accurate for statement and line coverage.

2. istanbul (AST Instrumentation)

• Mechanism: Injects counter variables into your JavaScript AST before execution (cov_213912.f[0]++).
• Performance: Slower because AST modification adds CPU overhead.
• Accuracy: Better handling of complex branch conditions in older transpiled codebases.

For modern TypeScript and ES module codebases, v8 is recommended for high speed and clean execution.