3 Commits

Author	SHA1	Message	Date
xCyanGrizzly	46cb517b8d	fix: use standard @prisma/client imports instead of custom output path ... The custom generator output to src/generated/prisma caused persistent Turbopack module resolution failures in CI. Switch to the standard @prisma/client import path which all bundlers resolve correctly. - Remove custom output from prisma schema generator - Update all imports from ../generated/prisma to @prisma/client - Add postinstall script to auto-run prisma generate after npm ci - Remove generated files from git (no longer needed in source tree) - Simplify CI workflow (remove verify step and --webpack workaround) Co-Authored-By: Claude <noreply@anthropic.com>	2026-02-18 19:49:53 +01:00
xCyanGrizzly	8436a0e875	fix: use relative imports for generated Prisma client ... Turbopack cannot resolve @/generated/prisma path alias during next build, even with the files committed and baseUrl set. Switch to relative imports (../generated/prisma) which Turbopack resolves without issues. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-18 17:44:43 +01:00
xCyanGrizzly	3a5726e82b	Init	2026-02-18 14:26:36 +01:00