The author argues multiple times that Next uses the React canary release channel and that's unstable. I think the name for this release channel might be mislead

The author argues multiple times that Next uses the React canary release channel and that's unstable. I think the name for this release channel might be misleading: "We’re introducing an officially supported Canary release channel for React. Since it’s officially supported, if any regressions land, we’ll treat them with a similar urgency to bugs in stable releases." And: "Unlike the Experimental channel, React Canaries only include features that we reasonably believe to be ready for adoption. We encourage frameworks to consider bundling pinned Canary React releases." While I think that Next.js 13's release was bumpy and about a year too early (let's blame it on the VCs), the App Router is in nice shape today and ready for production. It has a steep learning curve though and your brain needs to painfully unlearn some well-established patterns. Source: https://react.dev/blog/2023/05/03/react-canaries https://react.dev/blog/2023/05/03/react-canaries