Add reporters config and more documentation#18
Merged
NullVoxPopuli merged 2 commits intoMar 20, 2026
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds configurable built-in coverage reporters to the Testem middleware and updates the docs around coverage setup.
What changed
Added a new
reportersmiddleware option so consumers can choose which Istanbul-native reporters to generate.Kept existing behavior as the default when
reportersis not provided.Preserved compatibility for the text summary file in the default path, and when the text reporter is explicitly requested.
Added validation for the new config so invalid reporter values fail clearly.
Added integration coverage for a custom reporter configuration using
json-summaryandlcov.Expanded the README to document:
the new
reportersoptionhow reporter selection works
the requirement to enable
build.sourcemap: truein Vite so coverage maps back to source correctlythe need to set
distDirwhen the Vite build output is not distWhy
This makes coverage output configurable without needing custom post-processing for standard Istanbul report formats, while keeping the current default experience unchanged for existing users.