git-worktree-nextjs-prisma

New git worktrees lack the generated Prisma client and non-versioned environment files, causing runtime errors. You must copy the .env files and run npx prisma generate in the new worktree to resolve this.

To set up git worktrees for Next.js with Prisma, create the worktree, copy environment files, run npm install, and execute npx prisma generate. This ensures the Prisma client and configs are present for isolated feature development.

Generating the Prisma client in parallel git worktrees requires copying non-versioned .env files into the worktree, installing dependencies with npm install, and running npx prisma generate to produce the client locally.

Yes, git worktrees support parallel UI variant development and bug fixing without breaking Prisma. Enforcing deterministic steps like npm install, npx prisma generate, and proper environment handling stabilizes each isolated worktree.

To fix missing environment files in a Next.js worktree, copy the non-versioned .env files from your main repository into the new worktree directory. This prevents missing configuration errors during local development.

Yes, Prisma requires running npx prisma generate in every git worktree. Because the generated client is not versioned, each isolated worktree must produce its own client to avoid runtime errors during development.