Use Intern's own coverage integration before introducing another collection wrapper.

Which files should Intern instrument? Should the report name built JavaScript or original source? Its coverage setting selects application files, while reporters publish the results. Keep both separate from the suite configuration that decides which tests run.
Target the files that execute
This fragment assumes an existing Intern project whose test build writes JavaScript beneath build/src. Preserve the working suites, environments and connection settings.
Intern configuration fragment
{
"coverage": "build/src/**/*.js",
"reporters": ["runner", "htmlcoverage", "jsoncoverage"]
}The official integration documents htmlcoverage and jsoncoverage as Intern reporter names. Direct nyc commands use html and json. The shared data format does not make runner options interchangeable.
Separate build paths from source paths
The coverage glob must find the JavaScript the environment loads. Maps connect that code to TypeScript or another original source. First confirm that the executed build appears, then inspect its original filename and one known conditional.
Intern's Istanbul tutorial describes instrumentation for local Node loading and remote browser tests. Identify the application asset the browser actually uses, especially when development and test servers serve different builds. Merely opening the intended URL does not prove it served instrumented code.
Trace a missing result
| Symptom | Inspect first |
|---|---|
| No files reported | Build output and coverage glob. |
| Node appears; browser does not | The browser’s served test build and collection. |
| Paths point into build output | Maps and original source availability. |
| Unknown reporter name | Intern aliases rather than nyc flags. |
A useful probe is a function with two returns. Exercise one outcome, confirm the other is uncovered, then add its assertion. This tests collection more directly than checking whether an output directory exists.
Keep configuration with its runner
Use documentation matching the Intern release in the project. The official tutorial explains an integration, not compatibility with every modern loader or browser driver. If Intern already produces Istanbul JSON, use the coverage-object workflow to render another output rather than instrumenting the build twice.
Primary sources
Check official documentation against the tools installed in your project. These explanations and examples are independent.