openclaw - 💡(How to fix) Fix [Feature]: Move vitest config files into a vitest/ directory [2 comments, 1 participants]

Summary

Consolidate ~10+ root-level vitest config files into a vitest/ subdirectory to reduce root clutter. IT LOOKS REALLY UGLY

Problem to solve

The project root contains dozens of vitest.*.config.ts and related path files, making it hard to navigate and find important files like package.json, README.md, or tsconfig.json. The root ls output is dominated by test configs.

Proposed solution

Move all vitest..config.ts and vitest.-paths.mjs files into a vitest/ directory at the project root. Update all references in package.json scripts, CI workflows, and any other tooling to point to the new paths.

Alternatives considered

Using Vitest's workspace feature (vitest.workspace.ts) to replace individual configs — more powerful but higher risk and larger refactor. Colocating configs with their respective packages — better long-term but a much bigger change touching many packages.

Impact

Affects all contributors. Low severity (annoying, not blocking). Pain occurs every time someone browses the repo root. Consequence is reduced readability and a messy first impression of the codebase.

Evidence/examples

Running ls in the repo root returns 100+ entries, roughly half of which are vitest configs. Also it's UGLY!

Additional information

No response