Affected version
Reports that share this version, grouped in one feed.
The upgrade codemod modifies eslint from a caret range to an exact latest major (10.10.0) even when target Next.js peer dependencies allow ESLint 9, causing peer dependency conflict with eslint-plugin-import and aborting the upgrade.
When a route segment uses <Suspense fallback={null}> and the content suspends initially, the InnerScrollHandler effect in layout-router.tsx returns early because no client rects are available, preventing the expected scroll-to-top on navigation. The scroll only occurs on a later navigation. A ResizeObserver-based fix ensures the effect reruns once the suspended content lays out.
With pnpm v11's enableGlobalVirtualStore enabled, node_modules/next is a symlink to a global store outside the project root. Turbopack's filesystem resolution restricts access to the project root, causing 'Couldn't find the Next.js package' in dev mode. Webpack works; this is a Turbopack-specific limitation.
When a navigation clicks a Link during an in-flight prefetch, a pending segment-cache entry is passed to React as a plain promise. In partial or rejected prefetches the promise resolves to null, causing React to commit an empty segment and drop the document title.
The @next/codemod next-lint-to-eslint-cli transform hardcodes npx to run @eslint/migrate-config, which is incorrect for pnpm projects and can lead to package manager mismatch, lockfile pollution, or failures in strict environments.