You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I navigate directly to /test1, Next.js automatically makes an RSC (React Server Components) request once for /test2 and /test3. After that initial load, when I click between links, the RSC request repeats every time I click /test1, whereas for the other routes, it appears to remain cached.
Similarly, if I navigate directly (or refresh) to /test2, Next.js automatically issues an RSC request once for /test1 and /test3. However, clicking repeatedly on /test2 results in an RSC request every single time.
Why does this behavior occur? Why isn't the route I initially land on added to what appears to be the router's cache, resulting in a repeated RSC request each time I navigate to it again? Additionally, I've noticed that for this initial route, the RSC request includes the manifest and favicon requests, while for other routes fetched in the background, the RSC request occurs only once.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
When I navigate directly to /test1, Next.js automatically makes an RSC (React Server Components) request once for /test2 and /test3. After that initial load, when I click between links, the RSC request repeats every time I click /test1, whereas for the other routes, it appears to remain cached.
Similarly, if I navigate directly (or refresh) to /test2, Next.js automatically issues an RSC request once for /test1 and /test3. However, clicking repeatedly on /test2 results in an RSC request every single time.
Why does this behavior occur? Why isn't the route I initially land on added to what appears to be the router's cache, resulting in a repeated RSC request each time I navigate to it again? Additionally, I've noticed that for this initial route, the RSC request includes the manifest and favicon requests, while for other routes fetched in the background, the RSC request occurs only once.
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions