Revalidate is re-rendering root layout when I believe it should not #59037
Replies: 4 comments 2 replies
-
Hello @mattkauffman23 . did you find any solution to this. I am currently experiencing the same problem |
Beta Was this translation helpful? Give feedback.
-
Unfortunately I did not. |
Beta Was this translation helpful? Give feedback.
-
Same issue here, I tried calling revalidatePath with different arguments, but the console log in the root layout always gets printed on the server side. |
Beta Was this translation helpful? Give feedback.
-
any updates on this i took face the same issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
It's possible I don't understand how revalidatePath is supposed to work, but wanted to confirm.
I have a server action that revalidates a path like this:
revalidatePath("/(dashboard)/connections", "page");
I expected that to trigger a re-render for any pages / layouts downstream of
connections
but I'm seeing the root layout re-render. It's particularly noticeable because I'm using custom fonts that cause a bunch of layout shifts when the root layout reloads them.My question is does revalidating a route re-render the entire page for that route inclusive of ancestor layouts or should it only re-render pages / layouts from that route segment down?
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions