Critical: Build Errors Ignored in Production Configuration

[AliiiBenn]

Priority

🔴 Critical - Production Safety Issue

Location

next.config.mjs:15-24

Problem Description

The Next.js configuration is set to ignore both ESLint and TypeScript errors during production builds:

eslint: {
  ignoreDuringBuilds: true,
},
typescript: {
  ignoreBuildErrors: true,
}

Impact

• Code with type errors can be deployed to production
• Linting errors that could prevent bugs are silently ignored
• Reduced code quality and reliability
• Potential runtime errors from unchecked code
• False sense of security during CI/CD

Why This Matters

TypeScript and ESLint are safety nets. Ignoring them defeats their purpose and allows:

1. Undetected null pointer errors
2. Missing error handling
3. Incorrect prop types
4. Unused/dead code in production bundle

Expected Behavior

Remove both configurations to enable proper checking:

// Remove these entirely - let the errors block builds
eslint: {
  // Only ignore in development if absolutely necessary
  ignoreDuringBuilds: false, // or remove the key
},
typescript: {
  ignoreBuildErrors: false, // or remove the key
}

Steps to Fix

1. Remove the ignoreDuringBuilds and ignoreBuildErrors options
2. Run pnpm build to see all current errors
3. Fix all TypeScript errors
4. Fix all ESLint errors
5. Re-run build to ensure clean state

Related Issues

• Critical: Syntax Error in auth.ts Configuration #3 - Inconsistent .env.example contributes to build confusion

Additional Context

The presence of these ignores suggests there are existing errors that need to be addressed. This should be a top priority before any production deployment.