Oxlint, a Rust-based JavaScript and TypeScript linter developed as part of the Oxc toolchain, has reached its first stable release. The 1.0 milestone brings a combination of fast linting, extensive rule coverage, and migration tools aimed at making adoption straightforward for both open-source projects and large enterprises.
Oxlint v1.0 ships with over 520 supported ESLint rules, multi-file analysis capabilities, and zero-configuration defaults. The project’s maintainers claim performance improvements of 50-100x over ESLint in real-world scenarios, with benchmarks showing codebases that previously took minutes to lint now completing in under a second.
Oxlint can handle multi-file rules efficiently. Examples include import/no-cycle and oxc/no-barrel-file, which require resolving dependencies across many files. In Airbnb’s internal testing, Oxlint was able to run these rules over a repository containing more than 126,000 files in just 7 seconds. A task ESLint could not complete in the same environment due to timeouts.
The out-of-the-box experience for Oxlint is designed to be minimal and, right now, can be used only to fully replace ESLint in small to medium projects.
Developers can get started with a single command:
npx oxlint@latest .
Oxlint’s zero-config mode is designed for quick adoption, enabling developers to start linting immediately. For teams that need more customization, Oxlint provides support for .oxlintrc.json configuration files modeled after ESLint’s v8 flat config system. This approach supports nested settings, rule overrides, and extendable shared configurations.
To simplify migration, tools such as oxlint-migrate and eslint-plugin-oxlint are available, enabling developers to convert existing ESLint setups and even run both linters side-by-side during a gradual transition. Larger projects are advised to use the eslint-plugin-oxlint plugin, which will turn off any ESLint rules already supported by Oxlint, allowing both to run simultaneously until you are able to migrate fully.
The linter supports over 520 rules, and the rule set continues to grow. New rules are being reviewed and added from sources such as eslint core, typescript-eslint, eslint-plugin-react, eslint-plugin-vitest and more. A full list is available on the GitHub product plan.
Developer feedback has been largely positive. On Reddit, one user commented:
I just migrated from ESLint for one of my projects, and the experience has been pretty good. It’s very fast, I could replace about 5 or 6 dependencies with just one, and the configuration format is much easier. Previously I decided not to use Biome because the Formatter doesn’t support Tailwind class ordering yet, now I’m running Oxlint with Prettier.
Oxlint’s performance is attributed to its Rust-based architecture and shared Oxc parser, which, according to their benchmarks, is 50 – 100x faster than ESLint and even 2x faster than Biome.
Extensions are already available for usage within various IDEs, such as VSCode, IntelliJ and WebStorm, and Zed Editor.
The maintainers note that Oxlint currently does not support type-aware rules, though this is under consideration for future releases. Support for custom ESLint style plugins is also planned.
Oxlint is available as an open-source package on npm and can be integrated into local development, CI/CD workflows, or monorepos. Full documentation and migration guides are available at oxc.rs, along with more information about other tools available in the Oxc toolchain.
