`static` Router Cache is used once, the value of `staleTimes.dynamic` is applied the next time. about next.js HOT 3 OPEN

Ahh, I see what you mean @AkifumiSato -- let me take a closer look at why we needed that condition and I'll get back to you!

from next.js.

Hi @AkifumiSato -- the names "static" and "dynamic" do not relate to the page rendering type, but rather different categories of "liveness" that can be configured. The actual heuristic of whether to use dynamic or static is based on the prefetch prop. From the docs:

The dynamic property is used when the prefetch prop on Link is left unspecified.
The static property is used when the prefetch prop on Link is set to true, or when calling router.prefetch.

The different properties of this config refer to variable levels of "liveness" and are unrelated to whether the segment itself is opting into static or dynamic rendering. In other words, the current static default of 5 minutes suggests that data feels static by virtue of it being revalidated infrequently.

So in this case, static will influence:

• How long a loading.js segment is held onto before being refetched from the server
• How long a segment with prefetch={true} will be held onto before being refetched from the server.

If you modify the Link components to have prefetch={true}, you'll see that your static staleTime property is used.

Let me know if I misunderstood your question!

from next.js.

@ztanner Thank you for response.

The dynamic property is used when the prefetch prop on Link is left unspecified.

I tried with prefetch={undefined} for a static rendered page and staleTimes.static was applied until the cache was first used. After the second time, staleTimes.dynamic is applied. This seems to be caused by isFirstRead.

I think the documentation needs to be changed to describe up to the first use of the cache or to a simpler specification. What do you think?

from next.js.