4 ms·
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
by austinkhale 4y ago
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-in-nextjs/ https://adamwathan.me/2019/10/17/persistent-layout-patterns-...) but having first-class support for this paradigm will be awesome.
- leerob 4y agoThank 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. [1]: https://nextjs.org/docs/basic-features/layouts https://nextjs.org/docs/basic-features/layouts
- dalmo3 4y agoThere's a fundamental flaw with the solution proposed in the documentation (getLayout as a function), which could be fixed by using a pure JSX approach: https://github.com/vercel/next.js/issues/36029 https://github.com/vercel/next.js/issues/36029
- nullcipher 4y ago"irrationally excited" - what does this phrase mean? that there is no basis for your excitement? sounds so cheesy
- bobkazamakis 4y agoexcited beyond reason? try lactaid.
- sdmike1 4y agobeing more excited that you can readily account for
- vgrafe 4y agoI 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?