Skip to main content
Oxlint is a blazingly fast JavaScript/TypeScript linter written in Rust that is 50-100x faster than ESLint. CodeRabbit runs Oxlint version 1.78.0.

​
Files

Oxlint will run on files with the following extensions:
  • .js
  • .mjs
  • .cjs
  • .jsx
  • .ts
  • .mts
  • .cts
  • .tsx
  • .vue
  • .astro
  • .svelte

​
Configuration

Oxlint supports the following configuration files:
  • .oxlintrc.json
  • oxlintrc.json
  • .oxlintrc
  • oxlint.json
CodeRabbit searches the repository recursively for the first supported config file outside common generated and dependency directories and GitHub Actions or CircleCI pipeline paths. It uses that config for every supported changed file in the run.
CodeRabbit only runs Oxlint when an Oxlint config file is present and Biome is disabled.
Oxlint is enabled by default. Enable or disable it with .coderabbit.yaml or the CodeRabbit web UI:
.coderabbit.yaml

​
Security policy and restrictions

CodeRabbit runs Oxlint in a sandbox. Because JavaScript-based plugins can execute repository-controlled code, CodeRabbit does not run Oxlint analysis when the Oxlint configuration enables them. A non-empty jsPlugins array at the top level or inside any overrides entry causes CodeRabbit to skip Oxlint analysis. Configurations that omit jsPlugins or set it to an empty array continue to receive Oxlint findings as before. Oxlint’s built-in plugins setting continues to work and does not affect eligibility.

​
When we skip Oxlint

CodeRabbit will skip running Oxlint when:
  • Oxlint is already configured in GitHub Actions, GitLab CI, CircleCI, or Azure Pipelines.
  • No Oxlint config file is found.
  • Biome is enabled.
  • The Oxlint configuration declares a non-empty JavaScript plugins array (jsPlugins) at the top level or inside any overrides entry.
  • The repository’s Oxlint configuration cannot be read, is not valid JSON, or does not parse to a JSON object.