hensei-web/app/[locale]
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
..
[username] fix: import useSearchParams from next/navigation instead of next-intl 2025-09-02 20:41:21 -07:00
new refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
p/[party] refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
saved fix: import useSearchParams from next/navigation instead of next-intl 2025-09-02 20:41:21 -07:00
server-error refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
teams fix: import useSearchParams from next/navigation instead of next-intl 2025-09-02 20:41:21 -07:00
unauthorized refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
error.tsx refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
global-error.tsx refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
layout.tsx refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
not-found.tsx refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00
page.tsx refactor: migrate App Router pages to locale segments 2025-09-02 20:19:47 -07:00