Consolidate Vitest configuration into vite.config.ts

[jrcity]

Summary

This PR resolves a configuration collision where Vitest was silently ignoring the Vite testing settings. It standardizes the project to use a single vite.config.ts for both bundling and testing, removing duplicate sources of truth.

What changed

• Consolidated all test configurations (including coverage targets) into vite.config.ts.
• Consolidated resolve.alias definitions into vite.config.ts so Vite natively shares the same path aliases as Vitest.
• Added @/* paths mapping to tsconfig.json for IDE and static type-checking support.
• Configured ./test/setup.ts as the sole test setup file and ensured @testing-library/jest-dom/vitest is globally injected.
• Added the /// <reference types="vitest" /> directive to vite.config.ts to strictly type the test configuration.
• Deleted redundant files: vitest.config.ts and vitest.setup.ts.

Testing performed

• npm test runs successfully, proving the setup file runs and injects jest-dom correctly (validated by vitest-setup.test.tsx).
• npm run build executes without alias resolution errors.
• npm run lint and tsc succeed, proving the new tsconfig.json paths resolve the @ alias properly.

Closes #16

[vercel]

@jrcity is attempting to deploy a commit to the Prisca's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
octraban	Ready	Preview, Comment	Jul 28, 2026 8:28pm