Next.js 16.2 brings updates for performance, AI agents, and Turbopack
The React framework has over 200 changes for the Turbopack bundler and aims to make the use of AI agents more efficient.
(Image: Peshkova / Shutterstock.com)
The Next.js team at manufacturer Vercel has completed version 16.2 of the React framework. Next.js is now said to be significantly faster, concerning the time-to-URL during development and rendering in applications. The performance of the Turbopack bundler has also been improved, and Next.js also has updates to offer for AI-assisted software development.
(Image: Stone Story / stock.adobe.com)
Enhance web applications with AI so they really improve? The online theme day enterJS Integrate AI on April 28, 2026, shows how this is done. Early bird tickets and group discounts are available in the online ticket shop.
Support for AI-assisted Development
In Next.js 16.2, a default AGENTS.md file is included in create-next-app. This gives AI agents access to the Next.js documentation for the version used right from the start of a project. This is intended to circumvent the problem that AI agents are trained with outdated data and are not aware of current APIs, which can result in incorrect code.
As an experimental CLI, next-browser is available. It allows AI agents to inspect a running Next.js application. The data that next-browser makes accessible to the agents includes browser-level data such as screenshots or network requests, as well as framework-specific insights from React DevTools and the Next.js Dev Overlay, including props, hooks, Partial Prerendering (PPR) shells, and error messages.
To use next-browser, developers install it as a skill:
npx skills add vercel-labs/next-browserThen they enter /next-browser into their AI agent, which can handle skills, for example Claude Code or Cursor.
Further information on the use of next-browser can be found in the GitHub repository.
Videos by heise
Turbopack Updates for Performance and Security
Since version 16, Next.js has been using the Turbopack bundler as standard. The current release brings numerous performance improvements, bug fixes, and compatibility updates for Turbopack – a total of over 200 changes have been incorporated.
One of the new performance features concerns the reloading of server-side code during development. Previously, require.cache was cleared for a changed module, as well as for all other modules in its import chain. This often led to more code than necessary being reloaded, for example unchanged node_modules. In Next.js 16.2, only the actually changed code is reloaded, which is enabled by Turbopack's knowledge of the module graph. This is intended to significantly improve the efficiency of server-side hot reloading.
The Next.js development team supports this with figures observed in real-time applications: 67 to 100 percent faster application refresh and 400 to 900 percent faster compilation time in Next.js are possible.
Another update focuses on security. The security standard Content Security Policy (CSP) is used to prevent attacks on websites such as Cross-Site Scripting (XSS). The common nonce-based method requires all websites to be rendered dynamically. Since this can limit performance, the Next.js team relies on the alternative Subresource Integrity (SRI). This calculates a hash for each script in advance and only allows the browser to execute scripts with approved hashes. In Next.js 16.2, Turbopack has experimental support for SRI.
Further information on the updates in Next.js 16.2, and specifically in the areas of artificial intelligence and Turbopack, can be found in the Next.js blog.
(mai)
