fix: P0 search blank-page — Suspense boundary for useSearchParams#453
Closed
itskai-dev wants to merge 2 commits intomainfrom
Closed
fix: P0 search blank-page — Suspense boundary for useSearchParams#453itskai-dev wants to merge 2 commits intomainfrom
itskai-dev wants to merge 2 commits intomainfrom
Conversation
P0 fix: search page rendered empty because useSearchParams() in a client component requires a <Suspense> boundary in Next.js 14+. - Split page.tsx into server wrapper + search-client.tsx - Server page provides Suspense boundary with loading skeleton - Added metadata export (title + description) - Fixed hardcoded text-[#F8FAFC] → text-foreground in result cards Build verified: next build passes clean. Part of task-1771432024242-cq9eaky1m
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
- Remove 'as any' casts in mcp-client.tsx (McpServer type already has fields) - Replace 'as any as' with 'as unknown as' in compatibility route Unblocks lint-test-build CI.
Collaborator
Author
|
Closing orphan PR — parent task (task-1771432024242-cq9eaky1m) is done. If this fix is still needed, reopen with updated branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P0 Fix: Search Page Blank
Problem: The search page at
/search?q=...renders only the nav — no search form, no results. The entire client component fails to hydrate during SSR.Root cause:
useSearchParams()in a"use client"component requires a<Suspense>boundary in Next.js 14+. Without it, SSR bails and the component renders empty.Fix:
page.tsxinto server wrapper +search-client.tsxclient component<Suspense>with loading skeleton fallbackmetadataexport for SEO (title + description)text-[#F8FAFC]→text-foregroundin result card titlesVerification:
next buildpasses clean (exit 0)○ /search(static with client boundary)Note: Root URL (
/) was investigated and is working correctly — serves proper HTML landing page.Part of task-1771432024242-cq9eaky1m