Oxlint apps_v1.63.0: New Linter Rules & Vitest Support

TL;DR

  • New ESLint and Vue linter rules added for broader code quality checks.
  • Jest rules split into Vitest-specific rules, enhancing testing framework support.
  • Introduced SARIF formatter and agent output mode for improved reporting and integration.

Key Changes

Features: This update introduces a range of new linter rules, significantly expanding Oxlint’s capabilities. New rules for ESLint include require-unicode-regexp, no-restricted-properties, and logical-assignment-operators. For Vue development, return-in-computed-property and no-deprecated-model-definition rules are now available.

A major focus is on testing framework support, with numerous Jest rules now split into dedicated Vitest rules. This includes rules like prefer-to-be, prefer-strict-equal, prefer-spy-on, no-standalone-expect, and many more. This separation provides more precise linting for Vitest projects.

Reporting and output options are enhanced with the introduction of a SARIF formatter and an agent output mode. These additions offer new ways to integrate linting results into security and analysis tools, improving automated code review processes. Developer experience is also improved with the SourceCode.getDisableDirectives method and autofix support for sort-keys with comments.

Bug Fixes: Several issues have been resolved to improve linter accuracy and stability. Fixes address problems in no-single-promise-in-promise-methods, prefer-array-some (preserving comparison fixes), and no-map-spread. Improvements were made to handle Astro files, JSDoc require-returns, and edge cases in no-extra-boolean-cast and no-constant-condition. Autofixing for sort-keys with comments is also refined, and adjacent fixes are now treated as overlapping.

Impact for QA Teams

QA teams benefit from enhanced code quality checks through new ESLint and Vue rules. The dedicated Vitest rules improve test code linting accuracy, reducing false positives and streamlining test maintenance. New SARIF reporting can integrate linting results into security and compliance pipelines, aiding in early defect detection.