test: update c8 exclude list

[btea]

Description

When executing node --run test:coverage locally, the output includes the JavaScript files printed in the www and out folders, which contain too much unnecessary information and interfere with viewing the truly useful information.

Validation

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run node --run test and all tests passed.
• I have check code formatting with node --run format:check & node --run lint.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
api-docs-tooling	Ready	Preview	Sep 15, 2026 2:53am UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.97%. Comparing base (136de98) to head (78d6247).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1100      +/-   ##
==========================================
+ Coverage   90.70%   91.97%   +1.27%     
==========================================
  Files         220      215       -5     
  Lines       21132    20840     -292     
  Branches     1991     1991              
==========================================
  Hits        19167    19167              
+ Misses       1958     1666     -292     
  Partials        7        7              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

api-links Generator

Performance estimate _{(single CI run)}

• Generation time: 38.8% faster (1.34 s → 820.00 ms)
• Peak memory: 5.8% higher (361.02 MB → 382.09 MB)

legacy-html Generator

Performance estimate _{(single CI run)}

• Generation time: 46.2% slower (28.97 s → 42.35 s)
• Peak memory: 3.5% higher (2.38 GB → 2.46 GB)

legacy-json Generator

Performance estimate _{(single CI run)}

• Generation time: 13.9% faster (9.21 s → 7.93 s)
• Peak memory: 1.6% higher (1.68 GB → 1.71 GB)

llms-txt Generator

Performance estimate _{(single CI run)}

• Generation time: 21.0% faster (9.29 s → 7.34 s)
• Peak memory: 9.8% lower (1.61 GB → 1.45 GB)

orama-db Generator

Performance estimate _{(single CI run)}

• Generation time: 0.2% slower (8.13 s → 8.15 s)
• Peak memory: 4.1% higher (1.74 GB → 1.81 GB)

web Generator

Performance estimate _{(single CI run)}

• Generation time: 0.7% faster (65.16 s → 64.68 s)
• Peak memory: 0.3% higher (3.57 GB → 3.59 GB)

[avivkeller]

Shouldn't e2e be included?

[btea]

The e2e directory contains only test-related files and configuration, not production code, so we can exclude it from the c8 coverage report. The E2E tests continue to run separately through test:e2e.

[bmuenzenmeyer]

@avivkeller are you satisfied with that answer?