App Router: Force static and revalidate?
Unanswered
DennisK posted this in #help-forum
DennisKOP
Hi!
When migrating to the app router, one thing I noticed was that there was quite some loading time per page. This has been solved by set the dynamic variabele to
When migrating to the app router, one thing I noticed was that there was quite some loading time per page. This has been solved by set the dynamic variabele to
force-static. My question is: would we lose the revalidate option per page? Or would it still refetch data and cache this?5 Replies
@DennisK Hi!
When migrating to the app router, one thing I noticed was that there was quite some loading time per page. This has been solved by set the dynamic variabele to `force-static`. My question is: would we lose the revalidate option per page? Or would it still refetch data and cache this?
you can still revalidate the page by either using revalidatePath or revalidateTag, to revalidate the page
@B33fb0n3 you can still revalidate the page by either using revalidatePath or revalidateTag, to revalidate the page
DennisKOP
And putting an export const revalidate or the next: {revalidate: 600} option in a Fetch call would also work? 🙂
Thanks!
that revalidates only the fetch request. I don't think that the whole page get revalidates. You tested that?
@DennisK u tested that?