Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
1–10 of 123 posts
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#2Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#3We're irrationally excited about this internally and we're super happy with how the Vercel team has continued to push Next.js forward. Thank you!
We're using a version of the persistent layout pattern Adam Wathan [blogged about](https://adamwathan.me/2019/10/17/persistent-layout-patterns-...) but having first-class support for this paradigm will be awesome.
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#4Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.
Excited to try this out in my next project :)
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#5Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.
Excited to try this out in my next project :)
Open to any feedback you have – we've already started work on the implementation, and will adjust as necessary based on the RFC discussion.
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#6We're irrationally excited about this internally and we're super happy with how the Vercel team has continued to push Next.js forward. Thank you! We're using a version of the persistent layout pattern Adam Wathan [blogged about]( https://adamwathan.me/2019/10/17/persistent-layout-patterns-... ) but having first-class support for this paradigm will be awesome.
Thank you! We've added documentation[1] on the current layouts solutions, which is similar to Adam's post. It's a good workaround, but I'm very excited for improving the developer experience here.
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#7Looks like a nice improvement, looking forward to trying this out.
Nested layouts was the one stumbling block we had with next and felt very odd that we had to invent our own TabPane component to handle this pretty common use case.
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#8Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.
Not seeing it in the article, but how are you handling `index` routing in the `app` folder? If you are putting it in the top directory (e.g. `/app/index.js`), is it not able to get a custom `layout.js` file (as that position is used for the global variant)?
If it's in an `index` folder (e.g. `/app/index/page.js`), how would one create a route for `example.com/index`?
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#9Will there ever be a fix or blessed workaround re: #32216?
https://github.com/vercel/next.js/discussions/32216
previously: https://github.com/vercel/next.js/issues/2581
Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
#10Could a smart person please compare and contrast this RFC and the ideas of remix.run?