Next.js Discord

Discord Forum

Not using useSearchParams in any of the pages but still getting errors.

Unanswered
Tropical Kingbird posted this in #help-forum
Open in Discord
Tropical KingbirdOP
 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/trending-news". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/trending-news". Read more: https://nextjs.org/docs/messages/prerender-error

 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/404". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error


 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/newszop-editions". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/newszop-editions". Read more: https://nextjs.org/docs/messages/prerender-error

 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/my-topics". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/my-topics". Read more: https://nextjs.org/docs/messages/prerender-error

 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/search". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/search". Read more: https://nextjs.org/docs/messages/prerender-error

 ⨯ useSearchParams() should be wrapped in a suspense boundary at page "/". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout

Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error


I am seeing this error when I am building the app, these bunch of pages throw some useSearchParams error but I am not using any of the hooks in any of these pages.

3 Replies

Did you check components as well? @Tropical Kingbird
It's not page specific
Like even stuff you import in the components will throw the same errors