From e70bdda5111dacf0375810ed8ad8c6a8372763af Mon Sep 17 00:00:00 2001 From: xCyanGrizzly Date: Wed, 18 Feb 2026 17:49:00 +0100 Subject: [PATCH] fix: use webpack build in CI to bypass Turbopack resolution bug Turbopack cannot resolve imports from src/generated/prisma even with relative paths and committed files. Switch to --webpack for CI build. Also add file verification step for debugging. Co-Authored-By: Claude Opus 4.6 --- .github/workflows/ci.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 99a3d95..f4af18f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -47,8 +47,17 @@ jobs: - name: Run database migrations run: npx prisma migrate deploy + - name: Verify generated files exist + run: | + echo "=== src/generated/prisma contents ===" + ls -la src/generated/prisma/ + echo "=== index.ts content ===" + cat src/generated/prisma/index.ts + echo "=== client.ts first 3 lines ===" + head -3 src/generated/prisma/client.ts + - name: Build (includes type check and lint) - run: npm run build + run: npx next build --webpack env: AUTH_SECRET: ci-test-secret-not-for-production AUTH_TRUST_HOST: "true"