I'm noticing the same behavior.

Likewise, also encountering this. Seems to directly contradict the purpose of the new app and layout convention!

Worth noting: using browser history doesn’t produce this error. It’s only when clicking a <Link />.

For anyone with the same problem. I was able to fix my issue with this article. Basically the useSearchParams hook on static pages makes those pages to be deopted into client side rendering.

Issue still happening with the latest canary 14.0.4-canary.25.

For anyone with the same problem. I was able to fix my issue with this article. Basically the useSearchParams hook on static pages makes those pages to be deopted into client side rendering.

There is no useSearchParams in the layout of the issue repo.

I am also facing this issue on the latest stable Next version 14.0.4

I have the same issue with the latest stable version, but instead of using Component I use parallel routes here's more if you want to try the problem https://nextjs-forum.com/post/1189895822251405382

@jk1x8 I tested the testing app you linked and I don't see any problems, the navbar render once on page reload but in navigation it dosn't re-render.

We have a similar issue:

An input field has the onChange => and there we set the value to the search param (router.replace).
After that the input loses focus, and I need to click into the input field again.

Same issue in my navbar using:

'use client'
import { useRouter } from 'next/navigation'
import Link from 'next/link'

strict mode off

same issue and i tried to reprouce it on sandbox and same thing.
the client component is getting rerendered on link navigation.
here is the example : https://codesandbox.io/p/devbox/next-playground-h96q9t

Same issue. When I try removing useEffects it works like dev

Facing the same problem, removed all usePathname, useParams, useSearchParams, still layout rerenders on the same page segment change

I encountered a similar issue involving a component utilizing 'use client' and React.memo. Upon removing the memo, it worked as expected.

Unfortunately, identifying the issue required several hours of troubleshooting. Next team should take care of it, or at the very least, add some note to their docs.

same here, I noticed this issue because I have a component inside which there is a useEffect hook in the root layout, and when I switched routes, the hook would get triggered which means the whole component would get re-rendered.

However, this just happened when I first visited those routes, but after it worked as expected. So, this is the default behavior or what? Because I was thinking the root layout component would just stay there, while only the {children} would get rendered

Same here. Using useEffect or useState in a "use client" component, imported into layout.js, causes full reload of page/layout when navigating to root (app/page.js). But does not re-render navigating to or between sub-routes (about/page.js or contact/page.js).

project
└─ app
   ├─ about
   │  └─ page.js
   ├─ contact
   │  └─ page.js
   ├─ layout.js
   ├─ page.js