Remove the duplicate and conflicting Vitest configuration

[priscaenoch]

Problem

There are now two competing Vitest configurations and two setup files in the repository:

• vite.config.ts declares test: { environment: "jsdom", globals: true, setupFiles: ["./test/setup.ts"] }
• vitest.config.ts declares its own test block with setupFiles: './vitest.setup.ts', coverage settings, and an @ path alias
• Both test/setup.ts and vitest.setup.ts exist

Vitest gives vitest.config.ts precedence over the test block in vite.config.ts, so the vite.config.ts test settings and test/setup.ts are silently ignored. Two sources of truth mean a contributor editing the wrong one sees no effect, and the @ alias and coverage settings only apply in one of them.

What needs to be done

• Choose one configuration file as authoritative (recommended: vitest.config.ts, since it already has coverage and the alias).
• Remove the test block from vite.config.ts, or delete vitest.config.ts and merge its settings into vite.config.ts.
• Delete the redundant setup file so only one remains, and ensure the surviving config points at it.
• Confirm the @ alias resolves in tests and in the app build consistently (if the alias is kept, it must also exist in vite.config.ts and tsconfig.json).

Files

• vite.config.ts
• vitest.config.ts
• test/setup.ts
• vitest.setup.ts

Acceptance deliverables

• Exactly one Vitest config and one setup file remain.
• Editing the surviving setup file demonstrably affects test runs.

Tests to pass

• npm test passes with the single configuration.
• A test asserting a jest-dom matcher passes, proving the setup file is loaded.

[jrcity]

I would like to contribute by consolidating the project's Vitest configuration into a single, authoritative source. Having duplicate configuration files and setup scripts introduces unnecessary complexity, makes onboarding harder for contributors, and can lead to changes being applied in the wrong place without any visible effect.

My approach will be to retain vitest.config.ts as the primary configuration since it already includes coverage settings and the @ path alias. I will remove the redundant test configuration from vite.config.ts, eliminate the duplicate setup file, and ensure the remaining setup file is correctly referenced. I will also verify that the @ alias is consistently configured across Vitest, Vite, and tsconfig.json so both the application and test environment resolve imports identically.

Finally, I will run the full test suite, confirm that npm test passes, and add or verify a test using a jest-dom matcher to demonstrate that the surviving setup file is being loaded correctly.

Why I'm a Good Fit

I have experience working with React, TypeScript, Vite, and Vitest, and I value keeping project tooling simple, consistent, and easy for contributors to understand. Beyond making the tests pass, I focus on reducing maintenance overhead and ensuring the development environment remains predictable for future contributors.

[grantfox-oss]

🦊 GrantFox — @jrcity has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #16)
2. Your PR will be reviewed by the octraban maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@jrcity's PR #33 was approved and merged by @priscaenoch.

🏆 @jrcity: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @jrcity! Keep contributing to octraban.