Next.js adoption note

Next.js remains one of the most-used React frameworks, even as its maintainers and users keep arguing over how its routing system should work. (npmjs.com) (nextjs.org) Next.js is a framework built on React, the user interface library, and it adds tools for routing, rendering, data fetching, and builds. The `next` package was published again four days ago as version 16.2.3, and npm lists more than 60,526 packages in the registry using it. (nextjs.org) (npmjs.com) Routing is the part of a web framework that maps a URL to a screen, like a table of contents sending readers to the right chapter. Next.js now documents two routing systems: the newer App Router and the older Pages Router. (nextjs.org 1) (nextjs.org 2) The App Router uses a file-based system and adds newer React features including Server Components, Suspense, and Server Functions. The Pages Router is still supported in current releases, and the docs say it is still being improved. (nextjs.org 1) (nextjs.org 2) That split helps explain why router debates keep surfacing around Next.js. Teams starting fresh can use the App Router for newer React patterns, while older codebases can stay on the Pages Router without rewriting everything at once. (nextjs.org 1) (nextjs.org 2) The company’s own documentation now treats the App Router as the default path for new learning materials. The docs homepage sends new users first to “create your first application” with the App Router, while keeping a separate documentation track for the Pages Router. (nextjs.org) (nextjs.org) The technical tradeoff is partly about React versions as well as folder structure. Next.js says the App Router ships with built-in React canary releases that include stable React 19 changes and newer features, while the Pages Router uses the React version pinned in a project’s own package file. (nextjs.org) That means the argument is not only about taste or syntax. It is also about whether developers want earlier access to newer React capabilities or a more conservative path for existing applications. (nextjs.org) Tim Neutkens, one of Next.js’ authors, made the adoption point during that wider routing discussion, using npm download volume to argue that many developers are still choosing the framework at scale. The public npm package page confirms the package remains heavily used and actively updated. (github.com) (npmjs.com) For now, the practical message from the docs is coexistence: Next.js supports both routers, recommends the newer one for the latest features, and leaves older projects a maintained path forward. (nextjs.org) (nextjs.org)