test: collect coverage from untested files too

[AriPerkkio]

🔗 Linked issue

(looks like everyone leaves this empty)

🧭 Context

Currently code coverage is not collected from untested files. You'll need to define coverage.include to instruct Vitest which files are considered as source files.

https://vitest.dev/guide/coverage.html#including-and-excluding-files-from-coverage-report

📚 Description

Defines source directories in coverage.includes with extensions of ts and vue.

This drops code coverage:

  --------------------------------------------|---------|----------|---------|---------|
  File                                        | % Stmts | % Branch | % Funcs | % Lines |
  --------------------------------------------|---------|----------|---------|---------|
- All files                                   |    59.1 |    45.68 |   54.58 |   60.41 |
+ All files                                   |   44.05 |    37.21 |   41.92 |   44.26 |

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Mar 28, 2026 1:06am
npmx.dev	Ready	Preview, Comment	Mar 28, 2026 1:06am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Mar 28, 2026 1:06am

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• release

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e71db7ff-3fc7-4ece-ad5b-ee898b4f05af

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Updated vite.config.ts to adjust Vitest v8 coverage configuration: added an include filter {app,cli,server,shared}/**/*.{ts,vue} and retained the existing exclude filters **/node_modules/** and **/*.json. Coverage collection is now explicitly targeted to .ts and .vue files under the app, cli, server and shared directories.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly explains the context, rationale, and impact of adding coverage.include configuration to Vitest, with specific file changes and metrics provided.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ghostdevv]

I re-added the exclude as I think it should still be there? WDYT?

Also the CI has been failing, any ideas? If not I'll try and take a look soon 🙏 I'll mark as draft while we work on that, and then we can make it ready again when it's working!

[AriPerkkio]

I re-added the exclude as I think it should still be there? WDYT?

*.json does not match the include glob's extensions (.ts, .vue) so it's not needed at all. Does app/, cli/, server/ or shared/ directories contain node_modules? 🤔

Also node_modules is always excluded so it doesn't need to be added. https://github.com/vitest-dev/vitest/blob/1f2d318493363855b66a22caaf7c1c10579029d5/packages/vitest/src/node/config/resolveConfig.ts#L497-L523

Also the CI has been failing, any ideas? If not I'll try and take a look soon 🙏 I'll mark as draft while we work on that, and then we can make it ready again when it's working!

No idea really. Tests should not fail based on collected coverage.

[ghostdevv]

I re-added the exclude as I think it should still be there? WDYT?

*.json does not match the include glob's extensions (.ts, .vue) so it's not needed at all. Does app/, cli/, server/ or shared/ directories contain node_modules? 🤔

Also node_modules is always excluded so it doesn't need to be added. vitest-dev/vitest@1f2d318/packages/vitest/src/node/config/resolveConfig.ts#L497-L523

yeaaa you right, I kinda hoped it'd fix CI though 😆

Also the CI has been failing, any ideas? If not I'll try and take a look soon 🙏 I'll mark as draft while we work on that, and then we can make it ready again when it's working!

No idea really. Tests should not fail based on collected coverage.

🫠

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!