From 57ce1bffb285c9bc441a00b10453713ecdd8304a Mon Sep 17 00:00:00 2001 From: xCyanGrizzly Date: Wed, 18 Feb 2026 17:29:27 +0100 Subject: [PATCH] =?UTF-8?q?fix:=20remove=20standalone=20tsc=20step=20?= =?UTF-8?q?=E2=80=94=20next=20build=20handles=20type=20checking?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .github/workflows/ci.yml | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index b527e7a..99a3d95 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -42,20 +42,12 @@ jobs: run: npm ci - name: Generate Prisma client - run: | - 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" + run: npx prisma generate - name: Run database migrations run: npx prisma migrate deploy - - name: Type check - run: npx tsc --noEmit - - - name: Build + - name: Build (includes type check and lint) run: npm run build env: AUTH_SECRET: ci-test-secret-not-for-production