fix: remove standalone tsc step — next build handles type checking

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>
This commit is contained in:
xCyanGrizzly
2026-02-18 17:29:27 +01:00
parent b8a939a4f6
commit 57ce1bffb2

View File

@@ -42,20 +42,12 @@ jobs:
run: npm ci run: npm ci
- name: Generate Prisma client - name: Generate Prisma client
run: | run: npx prisma generate
npx prisma generate
echo "--- Checking generated output ---"
ls -la src/generated/prisma/ || echo "ERROR: src/generated/prisma/ does not exist!"
echo "--- Checking node_modules/.prisma ---"
ls -la node_modules/.prisma/client/ 2>/dev/null || echo "No .prisma/client in node_modules"
- name: Run database migrations - name: Run database migrations
run: npx prisma migrate deploy run: npx prisma migrate deploy
- name: Type check - name: Build (includes type check and lint)
run: npx tsc --noEmit
- name: Build
run: npm run build run: npm run build
env: env:
AUTH_SECRET: ci-test-secret-not-for-production AUTH_SECRET: ci-test-secret-not-for-production