@PraiseYeezus

Basically, if there's data that Next can't know ahead of time, like a dynamic route or query params/search params or a cookie or header, the page is dynamic. If the data you need is accessible at build time and not just request time, it will default to static. If you want to avoid static pages altogether and never deal with caching, use the 'force-dynamic' exports.

@Aaronmoreno

So helpful. Thanks for breaking this down so simply

@_helloMrKeni

if your data on the page is obtained by using fetch() API, you can just set the revalidate in the fetch() API, since revalidating the data-cache will also revalidate the full-route-cache

@noeldolan518

V15 should fix a lot of this craziness! 😅

@alexandrmeyer

Well, I am struggling with revalidatepath always working in dev mode, and ignoring certain cases in production. Sometimes it requires additional refresh. Still debugging, so didn't come to a conclusion yet.

@reyghardackernen7213

So I'm not the one confused about all of these things