- Shipped
- July 7, 2026 at 11:37 PM UTC
- Author
- Kamo
- Commit
- 8b55b42
The prisma-client generator (engineType=client) bakes a content-hashed runtime specifier (@prisma/client-<hash>) into the Next build. The builder satisfied it via a pnpm-store symlink, but the runner's fresh `pnpm add` re-resolves peer deps (@types/react patch drift) into a different pnpm virtual-store path, so the specifier dangles at runtime: `Cannot find module **************** — 500ing every DB-backed route, which broke the analytics OTK login and the kamo-internal Analytics nav. Alias every hashed client the build references to the actually-installed @prisma/client (same version) and assert resolution.