Turbopack skips gitignored directories during module resolution in
next build. Since src/generated/prisma was in .gitignore, the build
on CI failed with "Module not found: Can't resolve '@/generated/prisma'"
even though prisma generate created the files.
Fix: commit the generated client and remove it from .gitignore.
Run `npx prisma generate` after schema changes to update.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The standalone `npx tsc --noEmit` can't resolve @/ path aliases
for generated Prisma client files on CI, even with baseUrl set.
next build already runs TypeScript type checking and ESLint via
its own bundler which handles path aliases correctly.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add ls output after prisma generate to verify files exist
before tsc runs. This will show whether the generated client
is in src/generated/prisma/ or elsewhere.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tsc requires baseUrl to be set for paths mapping to work.
Without it, @/* path aliases are silently ignored during
standalone tsc --noEmit, causing TS2307 errors for
@/generated/prisma imports in CI.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Move DATABASE_URL to workflow-level env so all steps can access it
- Add verification step to confirm prisma generate creates output files
- This should fix TS2307 'Cannot find module @/generated/prisma' in CI
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The migration_lock.toml was excluded by a gitignore pattern
(prisma/migrations/**/migration_lock.toml) which caused
`prisma migrate deploy` to fail in CI with no lock file present.
Prisma requires this file to be version-controlled.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Disable react-hooks/incompatible-library warnings for RHF watch()
and TanStack useReactTable() — these are false positives from the
React Compiler plugin
- Remove unused useDebounce import and variable from vendor-table
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
