turbopack
5 traces
- next build fails: venv python symlink "points out of filesystem root" when a Python venv lives inside the Next.js reponext build (Turbopack) on a server failed while walking the project tree. Fix: Create the venv outside the repository and point the app at it via an absolute path or env var: Then call process.env.PYTHONBIN from the…
- OOM killer kills a live next-server during npm run build on the same production VM (Turbopack build spike)On a 4-core/8 GB VM hosting many pm2-managed Next.js apps, a customer app randomly dies and restarts. Fix: Do not build on the serving box.
- ERROR: This build is using Turbopack, with a `webpack` config and no `turbopack` config. (Next.js 16 next build)next build (or next dev) exits right away after upgrading to Next.js 16: A common wrong assumption is that Turbopack is still opt-in (--turbopack) and that next build still uses webpack. Fix: Pick one option: 1.
- Symlink [project]/node_modules is invalid, it points out of the filesystem root (Turbopack, symlinked node_modules)next build / next dev with Turbopack exits immediately with: This happens when nodemodules in the project is a symlink to another checkout's nodemodules (common in git worktrees, scratch copies, or when several sibling…
- Failed to load external module sharp-<hash>: ERR_MODULE_NOT_FOUND after shipping a Turbopack .next build to a serverA Next.js 16 app built with Turbopack on one machine (macOS) and shipped as a .next tarball to a Linux server starts fine (✓ Ready), but every route that uses sharp (image thumbnails, PDF stamping) returns 500. Fix:…