Affected version
Reports that share this version, grouped in one feed.
Next.js 16 with Turbopack generates external module references with content-based hashes that depend on the node_modules directory structure at build time. When deploying to a different environment and reinstalling dependencies (especially with pnpm symlinks), the hashes no longer match the installed packages, causing the production server to fail to start with 'Cannot find module' errors.
Turbopack's static analysis incorrectly treats the first argument of child_process.fork() as a module import, causing build failures when the argument is a dynamic path or absolute literal.
Next.js dev server calculates the V8 max-old-space-size based on host total memory (os.totalmem()), ignoring container memory constraints. In a Docker container with a memory limit, this sets an excessively high heap limit, potentially leading to out-of-memory (OOM) kills or performance degradation. Node.js already provides process.constrainedMemory() which respects cgroup limits; Next.js should use it when available.
When using Next.js 16 with Turbopack (default bundler), importing a native Node addon (built with napi-rs) from a separate package in a pnpm workspace during server-side prerendering results in `TypeError: (void 0) is not a function`. The package is added to `serverExternalPackages`, but Turbopack still bundles or mishandles the native module, causing the imported binding to be undefined.
When cacheComponents is true and htmlLimitedBots matches all bots, using runtime data (e.g. await connection()) inside generateMetadata causes Next.js 16 dev server to log 'did not produce a static shell and Next.js was unable to determine a reason', disrupting development and potentially affecting build/start.
In Next.js 16, lowering watchpack's aggregateTimeout from 200ms to 5ms causes the dev server's initial page scan to fire aggregation callbacks before the scan completes. The first partial aggregation builds the dynamic route table from an incomplete page list, so dynamic pages-router routes return 404 until a later aggregation rebuilds it.