Linting Violations
Reports rule violations from configured ESLint and Biome backends. Each finding links to the upstream rule documentation for context-specific guidance.
Linting rules encode community-validated patterns for correctness, style, security, and maintainability. The linting plugin runs the project's configured ESLint and Biome backends, surfaces violations as Vipr insights, and links to upstream rule documentation rather than re-authoring per-rule prose locally. This keeps the plugin in sync with rule-set updates without coupling the Vipr bundle to specific rule versions.
Severity guide
- info
- Style or formatting suggestion; safe to defer.
- warning
- A rule violation flagged by the configured linter; address when convenient.
- critical
- A rule violation the linter reports as an error in the project configuration.
Remediation
Fix the rule violation; consult the upstream rule documentation for guidance.
Each finding identifies the violating rule key (e.g., react-hooks/exhaustive-deps or
biome/noUnusedVariables) and the runtime message produced by the linter. When the
rule has an upstream documentation URL, the insight includes a direct link.
Fix strategy:
- Read the runtime message — most rules describe the violating pattern in plain text.
- Open the upstream rule documentation for context, examples, and exceptions.
- Apply the fix and re-run analysis to confirm the violation is cleared.
- If the rule is misconfigured for your codebase, suppress at the rule level in your ESLint/Biome config rather than per-occurrence — Vipr will respect the suppression.