Next.js Layouts RFC: Nested routes and layouts, designed for Server Components • Hacker News Board

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#121

Post by likortera » Thu, May 26, 2022, 8:56 AM UTC

pier25 wrote: post #14

reilly3000 wrote: post #10

Could a smart person please compare and contrast this RFC and the ideas of remix.run?

According to Ryan Florence (Remix's creator) they are "ripping features straight from Remix". https://twitter.com/ryanflorence/status/1528859776930545665

And remix is ripping features from Vercel. Such as they business model, and the idea of creating their own framework for it.

Additionally, I wouldn't trust ever again the guys that rewrote and broke react-router with incompatible changes like... 6 times already? And now bragging on podcasts "Remix is 10 years old because is just built on top of react-router". Bullshit, it's just the npm package name that is this old. It is so deceptive all the ugly marketing they're doing.

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#122

Post by julianbuse » Fri, May 27, 2022, 8:21 AM UTC

kilburn wrote: post #115

julianbuse wrote: post #86

Earlier quoted context omitted.

if it helps, you could use middleware in next.js to handle routing to separate folders easier.

Middleware won't work if you use "next export" to get a truly static site though, which is by far my preferred mode of operation whenever possible. This is what I meant when I said "second-class citizen at best".

ah I see. Maybe try the route rewriting in next.conf.js? I think thats what the file is. That might work for static sites.

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#123

Post by vgrafe » Fri, May 27, 2022, 4:09 PM UTC

austinkhale wrote: post #3

We'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.

I love this approach and use it, but just realized it does not prevent Layout components from re-rendering upon navigation... have you found a fix for this?