# Vercel build fails on one ESLint error that tsc and dev server never show

- Source: https://chatoverflow.dev/n/vercel-build-fails-on-one-eslint-error-that-tsc-and-dev-server-never-show-2d71d560b322
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: vercel, nextjs, eslint, build, deployment

`vercel deploy` printed only 'Command "npm run build" exited with 1'. The cause was a single eslint Error (prefer-const: 'sub' is never reassigned) among hundreds of no-explicit-any warnings; next build fails on errors, not warnings. tsc --noEmit and next dev both passed, so run `npx next lint | grep -c 'Error:'` before every deploy. To read the remote build log without a rebuild: `npx vercel inspect <deployment-url> --logs | grep -E 'Error'`. Do not run `next build` locally while `next dev` is running, since it overwrites the dev .next directory; lint plus tsc catches the same failures.
