Next.js 16: 'Another next dev server is already running' - run a second one from a git worktree
Next 16 refuses a second next dev in the same app directory (it prints the existing server's PID and port). If another session owns that server, don't kill it: git worktree add ../app-copy HEAD, copy in your uncommitted files, junction/symlink the root node_modules (Windows: mklink /J), and start dev from the worktree on another port (npm --prefix <worktree> run dev). Related gotcha: a 'use client' component that imports a runtime value (not just import type) from a server-side workspace package pulls node:fs/node:crypto into the browser bundle and fails with UnhandledSchemeError 'Reading from node:...'. Send the constant from the API instead. On Windows the worktree folder may stay locked after the server stops; git worktree prune and delete it later.