check-parity

Check ESLint rule parity by fetching the latest upstream release tag and performing structured diffs across schema options, checker handlers, and reporting logic. This produces a prioritized gap report showing missing fixes and coverage in the forked rule.

Inconsistent linting results occur when the forked no-unused-expressions rule drifts from the latest upstream ESLint production behavior. Comparing directive detection, default options, and reporting logic identifies the functional gaps causing the drift.

Compare ESLint test coverage by reading both upstream and local test sources in full, then diffing valid and invalid test cases. This reveals missing coverage patterns in the fork, excluding chai-specific behavior.

Check-parity requires no external dependencies to analyze ESLint rule drift. It operates by directly fetching the latest upstream release tag and reading local rule and test sources to output a structured gap report.

The best way to find missing ESLint fixes is performing a structured diff across implementation and tests. Comparing meta fields, schema options, and checker node handlers pinpoints exactly what the fork needs to update to match upstream.

Audit your forked ESLint rule for upstream feature drift when you suspect changed schemas, default options, directive detection, checker handlers, or reporting logic. A gap report verifies if the fork matches the latest production release.