ESLint and Prettier are configured
Why it matters
Without ESLint and Prettier, code style diverges with every commit. Reviewers spend time on formatting comments instead of logic. Style inconsistencies accumulate until they generate real merge conflicts. ISO 25010 maintainability.analysability and modifiability both degrade as the codebase becomes harder to read and predict. Projects bootstrapped with create-next-app get a default ESLint config that is never customized — it provides minimal coverage and gives a false impression that linting is configured.
Severity rationale
Medium because absent linting and formatting tools allow consistent, preventable code quality issues to accumulate that slow every code review and future refactoring.
Remediation
Install and configure both tools:
npm install -D eslint prettier eslint-config-prettier
npx eslint --init
echo '{}' > .prettierrc
For Next.js, extend the built-in config and add the Prettier integration:
// .eslintrc.json
{
"extends": ["next/core-web-vitals", "prettier"]
}
Add lint and format scripts to package.json. Pair with git pre-commit hooks (see the git-hooks check) so neither tool is optional.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Code Maintainability Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · maintainability.analysability — Analysability
- iso-25010:2011 · maintainability.modifiability — Modifiability
Taxons
History
- 2026-04-18·v1.0.0·Initial import from code-maintainability·automated