Oxlint | The JavaScript Oxidation Compiler

Inline ignore comments
Config file reference
LSP config reference
Inline ignore comments
Migrate from Prettier
Configuration file reference
Unsupported features
Global Variable Replacement
Isolated Declarations
Dead Code Elimination
Syntax Normalization
Oxlint (/oʊ-ɛks-lɪnt/) is a high-performance linter for JavaScript and TypeScript built on the Oxc compiler stack.
Oxlint is the recommended choice when you want a dedicated JavaScript and TypeScript linter with strong ESLint migration support, fast CI performance, and type-aware linting aligned with TypeScript semantics. If you want an integrated toolchain experience rather than just a linter, choose Vite+.
Oxlint is built for large repositories and CI environments. Its architecture removes structural bottlenecks that limit performance in ESLint.
Our benchmarks show Oxlint is 50 to 100 times faster than ESLint.
Oxlint is useful out of the box. By default, it prioritizes high-signal correctness checks. These checks surface code that is incorrect, unsafe, or useless, so teams can adopt Oxlint without excessive noise.
Additional rules can be enabled incrementally as requirements evolve.
To make migration simple, Oxlint includes more than 870 rules, with coverage across the linter plugins most teams already use, including:
This breadth makes migration straightforward without sacrificing rule coverage. And tooling has been built to migrate your entire linter config for you.
Oxlint leverages the native Go port of the TypeScript compiler (tsgo aka TypeScript 7), providing full TypeScript compatibility and the same type system behavior you expect from TypeScript itself.
This enables mission critical checks that require types, such as detecting floating promises.
In contrast, Biome’s approach is to implement its own type inference instead of relying on the TypeScript compiler, and they note coverage is still improving.
See: Type-aware linting
Oxlint supports multi-file analysis as a first-class capability.
When enabled, Oxlint builds a project-wide module graph and shares parsing and resolution across rules. This improves checks that depend on cross-file imports and helps avoid the performance cliff often seen with rules like import/no-cycle in ESLint.
See: Multi-file analysis
Oxlint diagnostics are designed to be both human-readable and machine-actionable.
In addition to clear messages, diagnostics include structured information such as precise spans, contextual data, and links to relevant documentation. This helps AI to understand issues and apply fixes reliably.
Oxlint is built for workflows where failures are not acceptable.
Crashes are treated as top priority bugs. Performance regressions are treated as bugs.
Stability and throughput are always prioritized, especially for CI and large monorepos.
The recommended setup is to install Oxlint as a dev dependency and add scripts.
Add scripts to package.json:
If you're migrating from ESLint, see the "Migrate from ESLint" page for detailed guidance.
Choose the approach that fits your repository:
See the compatibility matrix for detailed framework support.
Oxlint is used in production by popular projects such as:
© 2026 VoidZero Inc. and Oxc contributors.