Next.js Daily: Version Resolution and Scroll Fixes
The Next.js team merged three pull requests addressing version resolution for codemod tools, scroll behavior fixes for hoisted elements, and improved export error messaging. A new canary release v16.2.0-canary.46 was also published.
Duration: PT1M20S
Transcript
Good morning. This is Next.js Daily for February 15th, 2026.
Yesterday brought three merged pull requests to the Next.js codebase. Jiwon Choi merged a fix for the agents-md codemod tool that resolves version detection issues when package.json specifies Next.js with tags like "canary" instead of specific version numbers. The solution uses require.resolve() to properly identify the installed Next.js version, preventing documentation lookup failures.
Sebastian Silbermann merged changes to address a scroll behavior problem where hoisted React elements like stylesheets with precedence would prevent proper scroll-to-top functionality during page navigations. This fix is gated behind the experimental appNewScrollHandler flag and includes comprehensive test coverage for the router autoscroll functionality.
Jiwon Choi also merged improvements to export error messaging, adding path count information to make debugging export issues more informative for developers.
The team published Next.js v16.2.0-canary.46, updating version numbers across all packages in the monorepo.
What's next: The scroll handler improvements suggest continued focus on navigation UX refinements. The codemod tooling fixes indicate ongoing work to improve the developer migration experience.
That's your Next.js update for today.