364c155f9d
Fixes technical debt from Tasks 10, 18-20.
Problem:
- 38/46 frontend tests failing due to vi.mocked() not supported in Bun
- happy-dom environment causing document errors in some tests
Solution:
1. Replaced all vi.mocked(fn) calls with (fn as any) type casting
- useActiveClub.test.ts: 3 occurrences (localStorage mocks)
- auth-guard.test.tsx: 13 occurrences (useSession, useTenant, useRouter)
- club-switcher.test.tsx: 3 occurrences (useRouter)
- task-detail.test.tsx: 4 occurrences (useRouter, useTasks)
- task-list.test.tsx: 1 occurrence (useTasks)
2. Updated vitest.config.ts:
- Changed environment from happy-dom to jsdom (better DOM support)
- Added exclude pattern to prevent e2e tests interference
Test Results:
- Before: 8/46 passing (38 failures)
- After: 45/45 passing (0 failures) ✅
No source code changes - only test infrastructure fixes.
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.