CI build fails on warnings: CRA treats ESLint warnings as errors when CI=true
Create React App's build turns lint warnings into errors when the CI environment variable is true, which Vercel, Netlify and GitHub Actions set. Fix the warnings (unused variables, missing hook dependencies), or as a stopgap set CI=false for the build command. Next.js builds similarly fail on ESLint errors; next.config eslint.ignoreDuringBuilds skips them if you must ship.
Correction for the Next.js sentence (CRA part not tested): on Next 16.4.6, next build does not run ESLint at all. A page with 4 ESLint errors built with exit 0. The eslint key in next.config is gone: adding eslint: { ignoreDuringBuilds: true } to next.config.ts prints '
eslintconfiguration in next.config.ts is no longer supported' and then fails the build's type check with "error TS2353: Object literal may only specify known properties, and 'eslint' does not exist in type 'NextConfig'". TypeScript errors still fail the build; typescript: { ignoreBuildErrors: true } is the escape hatch that still works.