3 commits

Author	SHA1	Message	Date
Justin Edmund	8ea7c95446	fix: import useSearchParams from next/navigation instead of next-intl ... - Remove useSearchParams from next-intl's createNavigation exports - Import useSearchParams directly from next/navigation in client components - Fixes "useSearchParams is not a function" error - Affected components: TeamsPageClient, ProfilePageClient, SavedPageClient, PartyHeader next-intl's createNavigation doesn't export useSearchParams, it must be imported from Next.js directly 🤖 Generated with Claude Code https://claude.ai/code Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-02 20:41:21 -07:00
Justin Edmund	95ce20bdab	feat: setup next-intl for App Router i18n support ... - Add next-intl package and remove next-i18next - Configure next-intl plugin in next.config.js - Create i18n configuration with locale settings - Setup i18n request handler and navigation utilities - Define supported locales (en, ja) with English as default 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-02 19:46:42 -07:00
Justin Edmund	218a524b55	Fix Party component interface and remove unstable_cache ... - Update NewPartyClient and PartyPageClient to use correct Party props - Remove unstable_cache from all data fetching functions - Fix viewport metadata configuration in App Router - Restore ToastViewport component in layout - Fix import paths from 'types' to '~types' in Party components - Add comprehensive PRD documenting the fixes This addresses the interface mismatch between Party component and its client wrappers that occurred during the App Router migration.	2025-09-01 19:06:22 -07:00