I reported a bug months ago where app router hydration errors were occurring while copy and pasting example code directly from their official docs. Still hasn’t been fixed.<p>I will never recommend a project use Next for as long as I’m a software engineer. Maybe a bit dramatic, but a dumpster fire is brewing over at Next.
Completely agree with the point of middleware only supporting the Edge runtime. This borders vendor lock-in and continues to be an ongoing debate: <a href="https://github.com/vercel/next.js/discussions/46722">https://github.com/vercel/next.js/discussions/46722</a>. Hope they add the ability to switch to Node.js runtime.
I've had the encountered same problem when trying to just get the request path in order to highlight the current active page link in a navigation. It's simply not possible with Server Components only.<p>I ended up having to wrap each nav link in a client-side component, meaning the active state is lost in no-JS land (but will still render the nav on the server). The provider just wraps the link to provide a class, which can then be used to identify, with CSS, which link is active.<p>I really don't understand how cookies and headers can be provided, but not even just the requested path.
I started a project that is using Next.js 13 w/ Page Router (App Router was still in beta when I started it.) I haven’t looked much at App router yet, but what are the technical pros/cons of continuing to avoid it?
A pretty sad state of affairs. I really liked Next.js pre App Router but feel this new direction is not for me. Sure we can still use the legacy routing but they clearly steer towards App Router/RSC.
half-baked APIs seem to be par for the course with Next. Vercel feels like the Microsoft of React, trying to force everyone in the ecosystem to go through them. Gives me a cold prickly feeling!