Framework semantic default
Next.js next lint command removed unknown command ESLint remains installed
CI fails with unknown command even though ESLint remains installed.
Agent Quick Fix
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
Product: Next.js
Current-contract area: next lint command disappears from CI upgrade path
Likely root cause: CI fails with unknown command even though ESLint remains installed.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.Validation Status
Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.
Symptom
CI fails with unknown command even though ESLint remains installed.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
Verification
Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Next.js next lint command removed unknown command ESLint remains installed
site:nextjs.org docs next lint removed Next.js 16
Next.js 16 next lint removed
next lint removed use eslint cli nextjs.org
https://nextjs.org/docs/app/api-reference/cli/next
https://nextjs.org/docs/app/guides/upgrading/version-16
'next lint Command' in https://nextjs.org/docs/app/guides/upgrading/version-16