lint-check

Run ESLint and TypeScript type checks on modified frontend files by applying static analysis to git diff output. The tool automatically detects changed files and generates a structured report categorizing ESLint errors, TS type errors, and a11y violations.

Check web frontend code for accessibility and WCAG issues by running jsx-a11y linting and a11y validations. This identifies missing ARIA labels and poor contrast, surfacing violations alongside ESLint errors and TypeScript type errors in a consolidated report.

The best way to combine ESLint and TypeScript checks before a merge is running a comprehensive frontend linting pass. This assesses code style, potential errors, and type discipline, generating suggested fixes for modified files or the entire project.

Yes, the lint check works on the entire project when no git changes are detected. It defaults to analyzing modified files via git diff but seamlessly falls back to a full project scan to ensure all code quality issues are surfaced.

You need static analysis for frontend code quality to automatically catch code style issues, enforce TypeScript type discipline, and identify accessibility violations. This prevents potential errors and WCAG compliance issues from reaching production after merging multiple components.

Yes, you can use this lint check for projects without external dependencies. It operates with no required dependencies, using profile settings for language and dependencies to perform ESLint, TypeScript, and accessibility validations independently.