This issue is the general tracker for things we need / should do when Node.js v24 becomes LTS in October, and Next.js 16 is released: ### Node.js v24 LTS - Remove npm re-installation (Added in #8091) - Update the `.nvmrc` - Update `@types/node` ### Next.js v16 - #8207 (See https://nextjs.org/blog/next-16-beta#improved-caching-apis + https://react.dev/blog/2025/10/01/react-19-2#cache-signal) - Possibly use [`turbopackFileSystemCacheForDev`](https://nextjs.org/blog/next-16-beta#turbopack-file-system-caching-beta)? - Possibly use [The React Compiler](https://nextjs.org/blog/next-16-beta#react-compiler-support-stable) - Possibly use [`Activity` component](https://react.dev/reference/react/Activity)
This issue is the general tracker for things we need / should do when Node.js v24 becomes LTS in October, and Next.js 16 is released:
Node.js v24 LTS
.nvmrc@types/nodeNext.js v16
top-levelawait/React'scache()fornext-datain favour of'use cache'from Next.js #8207 (See https://nextjs.org/blog/next-16-beta#improved-caching-apis + https://react.dev/blog/2025/10/01/react-19-2#cache-signal)turbopackFileSystemCacheForDev?Activitycomponent