`cacheComponents: true` is incorrectly requiring Suspense boundaries for `useSearchParams()`
Unanswered
Cape lion posted this in #help-forum
Cape lionOP
16.0.1 with
cacheComponents: true is incorrectly requiring Suspense boundaries for useSearchParams() in a fully dynamic route that should not be prerendered. Attempted to wrap the component with useSearchParams() with Suspense boundaries at multiple levels (layout, page, and component), yet the build still fails with:⨯ Render in Browser should be wrapped in a suspense boundary at page "/auth/partner-signin"2 Replies
Cape lionOP
Attempting to make a clean reproduction but haven't managed to reproduce yet. My subject repo is complex.
@Cape lion 16.0.1 with `cacheComponents: true` is incorrectly requiring Suspense boundaries for `useSearchParams()` in a fully dynamic route that should not be prerendered. Attempted to wrap the component with `useSearchParams()` with Suspense boundaries at multiple levels (layout, page, and component), yet the build still fails with:
⨯ Render in Browser should be wrapped in a suspense boundary at page "/auth/partner-signin"
try removing some of the routes and see at which routes this error occurs