cookies in server side opts out of ssg, is client side a workaround?
Answered
Brown bear posted this in #help-forum
Brown bearOP
Hi, I have some pages where I have a very small component that needs to show data that is custom to a logged in user, to fetch this data in server side component I need to use the auth cookie to make a http call to an external server, this causes my whole page now to be dynamically rendered, if I move this small component to be a client component and I fetch the data on client side will this work and allow for this page to be static?
Answered by LuisLl
afaik, in Next.js you either have Static or Dynamic routes (default), not both unless you turn on PPR and place
<Suspense> boundaries appropriately. Any component nested inside of a page that's using Dynamic APIs will opt out of static rendering and turn your whole route dynamic.15 Replies
Brown bearOP
Nobody?
Yes it should work as long as you wrap your Client (and dynamic) component in <Suspense> and you have PPR (partial pre-rendering) turned on in your next config.
Also, make sure your server component page you’re trying to “SSG” doesn’t make use of any dynamic APIs (
And I believe it’s still needed to have PPR manually enabled in order to have both Static and Dynamic parts rendering in the same route.
Also, make sure your server component page you’re trying to “SSG” doesn’t make use of any dynamic APIs (
params, searchParams, cookies, headers) And I believe it’s still needed to have PPR manually enabled in order to have both Static and Dynamic parts rendering in the same route.
Brown bearOP
this seems to be a experimental feature
afaik, in Next.js you either have Static or Dynamic routes (default), not both unless you turn on PPR and place
<Suspense> boundaries appropriately. Any component nested inside of a page that's using Dynamic APIs will opt out of static rendering and turn your whole route dynamic.Answer
Brown bearOP
yes so it seems, unfortunately we only have 1 page which catches everything and there we were using dynamic API ...
You are using
params right? That alone makes your whole route dynamic, obviously cookies do too.Brown bearOP
yes
I don't know why the heck are we using 1 page for everything
bye bye static pages
@Brown bear Was the original question solved?
Brown bearOP
I guess so
but for params u can use generateStaticPaths or am I wrong?
generateStaticParams() is used to tell Next.js which dynamic pages you want to statically generate at build time. Since you’re providing the params ahead of time, Next.js can go ahead and have those pages ready and cached before you request them.
Brown bearOP
generateStaticSearchParams 
There’s not such thing tho