News for hackers. Stuff that matters.

A comment on One Year with Next.js App Router – Why We're Moving On. Parent comment

Re:One Year with Next.js App Router – Why We're Moving On by nvlled on Thursday October 30, 2025 @11:37AM (#45761226)
Why should it be the router? A saner option is to let the parent component coordinate the data fetches for the child components. What you are suggesting is way out of the normal responsibility of a router.
[ Parent | on HN ]
Re:One Year with Next.js App Router – Why We're Moving On by Swizec on Thursday October 30, 2025 @11:40AM (#45761253)
The router is just the most parenty component. It’s the component that takes some input (like a url) and uses what is essentially a giant switch statement to decide what gets rendered.
[ Parent | on HN ]
Re:One Year with Next.js App Router – Why We're Moving On by ricardobeat on Thursday October 30, 2025 @05:21PM (#45765521)
You could justify putting anything and everything in the router with this argument.
[ Parent | on HN ]