Adrien KISSIE

Since layouts can wrap multiple routes and **don’t rerender** on route changes, it cannot take these arguments as props. for the use cases you are looking for, NextJs. Provides some...

The thing is that if you use a `page.tsx` with multiple component (like a `Layout` component that wraps your entire page), with each page navigation you have (1) a rerender,...

@drewlustro , with next 13, you basically have to type your page yourself. Since the types are rather simple I don't think this is a big issue, but if you...

@drewlustro But if you want types for layout and other, I inspected myself the generated types by NextJs and created some custom types that I use for my project :...

I think you may need to install `experimental` version of **react** for it to work. Then again, the story around testing with app router is not yet complete so it...

Hello, i don't know if this is an expected behavior or not, but i've stumbled on this behvior a little while ago and traced it back to React ( link...

@dclark27 The key thing seems to be how it is supposed to work : https://twitter.com/sebmarkbage/status/1688622875702345728?s=46 Normally if you want to trigger suspense boundaries, you have to fetch your data in...

One thing @dclark27 CodeSandbox does not support streaming, so suspense won't work as expected.

@gfortaine > It looks like that you are doing [Client-Side Navigation](https://nextjs.org/learn/basics/navigate-between-pages/client-side) with a [Server Component](https://beta.nextjs.org/docs/rendering/server-and-client-components#server-components). Simply add the https://github.com/reactjs/rfcs/pull/227 at the top of the NestedPage component. Then, you will notice...

@gfortaine , the solution you’re suggesting is to use the `use` hook, but this hook lead to infinite fetches, so no it’s not a viable solution, at least for now....