validate-lint

Code style validation automatically detects and runs ESLint and Prettier on your project to enforce consistent formatting and catch style violations. Configure ESLint in .eslintrc or eslint.config.js, then run the validation to receive structured results showing errors, warnings, affected files, and violated rules.

Yes. Linting validation runs ESLint and Prettier as pre-commit checks to ensure all code adheres to style guides before commits are made. It returns pass/fail status and detailed violation data, making it suitable for quality gates and automated checks in CI pipelines.

ESLint requires a configuration file (.eslintrc, eslint.config.js, or package.json entry). Prettier is optional but recommended for formatting enforcement. Both tools work together in the validation process, with ESLint catching code quality issues and Prettier enforcing consistent formatting.

Validation returns structured output that pinpoints specific files with issues and lists the most frequently violated rules. This granular reporting helps developers target fixes efficiently rather than addressing all violations at once.

Linting validation categorizes violations into errors—critical issues that typically block commits—and warnings—less severe style inconsistencies. The output counts both separately so you can prioritize fixes based on severity.

Run validation before commits, during pre-refactor checks, and as a CI gate to catch style issues early. This prevents inconsistent code from reaching review and reduces merge conflicts caused by formatting differences across the team.