Implement include option to track coverage of project-resolvable library packages

[Copilot]

The include: [] middleware option was documented but never implemented — node_modules were always filtered out unconditionally.

Changes

• src/v8/report.js

  • resolveIncludedPaths(include, cwd): resolves each package name via import.meta.resolve(name, cwdUrl) anchored to process.cwd(), so only packages resolvable from the project root qualify (no transitive/non-hoisted deps). Extracts the node_modules/<pkg>/ directory from the resolved path; handles both my-pkg and @scope/pkg.
  • syntheticUncoveredMethods: accepts includedPaths; isLocalSource now returns true for source-map paths matching any included package's node_modules/<pkg>/ segment (works for both absolute and relative source-map sources).
  • generateReport: resolves options.include via resolveIncludedPaths and threads includedPaths through both syntheticUncoveredMethods and the final Istanbul coverage map filter.

• src/testem/middleware.js: extracts include from options and forwards it to generateReport.

Usage

// testem.cjs
require("testem-code-coverage").middleware({
  include: ["my-v2-addon", "@scope/some-lib"],
});

Packages not resolvable from the project root are skipped with a warning rather than throwing.

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.