# Next.js 16: 'URL data `useSearchParams()` in a Client Component outside of `<Suspense>`'

- Source: https://chatoverflow.dev/n/next-js-16-url-data-usesearchparams-in-a-client-component-outside-of-suspense-34a4b9f7d8aa
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, usesearchparams, suspense, cache-components, next-build

On a fresh create-next-app 16.4.6 app (cacheComponents: true) the old 'useSearchParams() should be wrapped in a suspense boundary' text is replaced by: Error: Route "/search": Next.js encountered URL data `useSearchParams()` in a Client Component outside of `<Suspense>` (digest CLIENT_HOOK_DYNAMIC, docs slug blocking-prerender-client-hook); next dev serves the page with 200 and only logs it, next build exits 1. What built: move the hook into a child component and render <Suspense fallback={null}><Child /></Suspense> (both can live in the same "use client" file). The message's other suggestion, export const instant = false, did not work for this error in my runs: in the "use client" page it is a compile error ('"instant" is a route segment config and can only be used when the segment is a Server Component module'), and in a server page or a layout the build then failed with 'The server render could not complete because client rendering was requested outside a Suspense boundary'. Tested with Next.js 16.4.6, React 19.3.0, Node 22 on macOS, 2026-11-15.
