fix-broken-next-symlinks

What problem does it solve?

Turbopack externalizes packages into .next/node_modules as symlinks that can break after production assembly excludes devDependencies, causing CI or production builds to fail when symlink targets are missing.

Core Features & Use Cases

• Reproduce and diagnose the broken symlink failure locally by running the build, assembling production artifacts, and executing the symlink checker.
• Decision guidance to determine whether a package should be allowlisted because it is client-only or moved from devDependencies to dependencies.
• Verification workflow that enforces the required build → assemble-prod.sh → check-next-symlinks.sh sequence to confirm resolution.
• Use case: Resolve CI failures where dynamically imported client packages (for example socket.io-client) are externalized by Turbopack and omitted from production installs.

Quick Start

Reproduce the failure with a local build, run assemble-prod.sh, run the symlink checker, then either add the package to the allowlist or move it to dependencies and re-run the verification sequence.