Page not deployed as ISR function
Unanswered
Masai Lion posted this in #help-forum
Masai LionOP
Hello! In my app, I have several dynamic pages, all using
Now, what this page does differently is using
revalidate and generateStaticParams. But one of them, /army-lists/[id] is not considered ISR by Vercel, and indeed I can see when I visit this page it's not very fast, meaning it's probably fetching data from the DB at runtime. What is weird is the build log shows the pages being prerendered: ├ ● /army-lists/[id] 1.47 kB 115 kB
├ ├ /army-lists/5fb1b9d9e1af06001770933c
├ ├ /army-lists/5fb1b9d8e1af0600177092fa
├ ├ /army-lists/5fb1b9d8e1af0600177092ec
├ └ [+652 more paths]Now, what this page does differently is using
searchParams on top of params (for optional stuff, like a modal). Can this be the reason?2 Replies
@Masai Lion Hello! In my app, I have several dynamic pages, all using `revalidate` and `generateStaticParams`. But one of them, `/army-lists/[id]` is not considered ISR by Vercel, and indeed I can see when I visit this page it's not very fast, meaning it's probably fetching data from the DB at runtime. What is weird is the build log shows the pages being prerendered:
├ ● /army-lists/[id] 1.47 kB 115 kB
├ ├ /army-lists/5fb1b9d9e1af06001770933c
├ ├ /army-lists/5fb1b9d8e1af0600177092fa
├ ├ /army-lists/5fb1b9d8e1af0600177092ec
├ └ [+652 more paths]
Now, what this page does differently is using `searchParams` on top of `params` (for optional stuff, like a modal). Can this be the reason?
yeah if you access the searchParams inside a server component, the page has to be dynamic.
you need to use useSearchParams + Suspense to access the search query instead, to make the page static
you need to use useSearchParams + Suspense to access the search query instead, to make the page static
Masai LionOP
Oh OK I will try to refactor my code to achieve this, thanks!