chore: remove per-module vite config files

[drazisil-codecov]

Summary by CodeRabbit

• Chores
  • Removed configuration files for the Vitest testing framework, impacting automated test coverage reporting and structured test result outputs.
  • Enhanced reporter configurations for improved testing report capabilities, including the addition of new reporters.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The pull request involves the deletion of multiple vite.config.ts files across various packages in the project. Each of these files contained configurations for the Vitest testing framework, which included settings for test coverage reporting, exclusion patterns for files, and specifications for output formats and reporters. The removal indicates a significant change in the testing strategy or framework employed in the project, potentially affecting automated test coverage and reporting mechanisms.

Changes

Files Grouped

Change Summary

packages/cli/vite.config.ts, packages/connection/vite.config.ts, packages/database/vite.config.ts, packages/gateway/vite.config.ts, packages/lobby/vite.config.ts, packages/login/vite.config.ts, packages/mcots/vite.config.ts, packages/nps/vite.config.ts, packages/patch/vite.config.ts, packages/persona/vite.config.ts, packages/sessions/vite.config.ts, packages/shard/vite.config.ts, packages/shared-packets/vite.config.ts, packages/shared.vite.config.ts, src/chat/vite.config.ts

Removed the vite.config.ts file, which contained configurations for the Vitest testing framework, including test coverage settings, exclusion patterns, output formats, and reporter specifications.

Possibly related issues

• Remove vite.config.ts from coverage listing #2096: The changes in this PR relate to the removal of vite.config.ts files, which aligns with the objective of removing these files from coverage listings.

Possibly related PRs

• chore: 🔧 setup commitlint to enforce conventional commits #2153: The changes in this PR involve the integration of testing into the pre-commit hook with the command make test, which relates to the testing framework configuration in the main PR. Both PRs focus on enhancing the testing workflow, although they address different aspects of it.

🐰 In the meadow, the rabbits play,
With configs gone, they hop away.
No more tests to run and hide,
In the fields, they now abide.
A new path they shall explore,
With leaps and bounds, forevermore! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[deepsource-io]

Here's the code health analysis summary for commits a5b058d..d3ccaef. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.11%. Comparing base (a5b058d) to head (d3ccaef).
Report is 1 commits behind head on dev.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #2155      +/-   ##
==========================================
- Coverage   28.98%   24.11%   -4.88%     
==========================================
  Files         224      217       -7     
  Lines       12329    11401     -928     
  Branches      557      338     -219     
==========================================
- Hits         3574     2749     -825     
+ Misses       8755     8652     -103     

Flag	Coverage Δ
cli	59.32% <ø> (+4.32%)	⬆️
connection	14.76% <ø> (-7.47%)	⬇️
database	23.71% <ø> (-7.25%)	⬇️
gateway	6.44% <ø> (-17.02%)	⬇️
lobby	6.03% <ø> (-1.18%)	⬇️
login	5.96% <ø> (-0.76%)	⬇️
mcots	8.63% <ø> (-2.00%)	⬇️
nps	5.76% <ø> (-9.83%)	⬇️
patch	71.42% <ø> (+7.00%)	⬆️
persona	16.68% <ø> (-2.33%)	⬇️
sessions	85.71% <ø> (-6.27%)	⬇️
shard	43.31% <ø> (-2.77%)	⬇️
shared	13.78% <ø> (-6.90%)	⬇️
shared-packets	0.00% <ø> (-2.66%)	⬇️
transactions	60.74% <ø> (ø)

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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud