OxLint — the new JavaScript Lint tool which is 50x faster than ESLint

Exciting news for developers! OxLint has officially launched, presenting itself as a JavaScript code-checking tool that rivals ESLint but boasts a speed nearly 50 times faster. Developed in Rust, OxLint eliminates the need for intricate configurations while efficiently catching errors and redundant code, making it a powerful addition to the developer’s toolkit.
Even Evan You, the creator of Vue.js, couldn’t help but express amazement at its blazing speed:

Let’s take a quick visual glimpse:

For a more in-depth performance comparison, head over to bench-javascript-linter.
How to Use OxLint
OxLint doesn’t aim to replace ESLint entirely. Instead, consider it as a performance-enhancing tool when ESLint’s speed becomes a bottleneck in your workflow. For example, projects running ESLint in lint-staged or CI setups may experience a significant speed boost, making linting tasks that used to take minutes now complete in seconds.
To test OxLint in your JavaScript/TypeScript codebase, run the following command in your repository’s root directory:
npx oxlint@latest # npm
pnpm dlx oxlint@latest # pnpm
yarn dlx oxlint@latest # yarn
bunx oxlint@latest # bun
deno run oxlint@latest # denoFor additional error details, the command line will provide comprehensive warnings. Additionally, there’s a VSCode plugin available; simply search for “oxc” in the plugin marketplace.
For more detailed information, refer to the Installation Guide.
OxLint’s Design Philosophy
1. Unmatched Speed
In real-world scenarios, Shopify reported that OxLint reduced their ESLint runtime from 75 minutes to a mere 10 seconds. Jason Miller, author of Preact, was astounded by OxLint’s speed, describing it as a massive victory. OxLint achieves its remarkable speed through key factors like Rust integration and parallel processing.
2. Focus on Code Correctness
OxLint prioritizes identifying errors, redundancies, or confusing code, emphasizing correctness over nitpicky rules. Categories like perf, suspicious, pedantic, or style are inspired by clippy's categorization rules. While this may seem unfamiliar at first, users find it incredibly convenient and user-friendly once accustomed.
3. Convenience in Use
Configuring new JavaScript/TypeScript codebases has become increasingly complex. OxLint addresses compatibility issues and potential hours of wasted time due to its zero-configuration approach. No configuration files or even Node.js are mandatory!
4. Enhanced Diagnostics
Understanding lint tool information can be challenging. OxLint simplifies this process by locating root causes and providing useful information. Error messages are designed to be easily comprehensible, aiding developers in quickly resolving issues.
5. Unified Rules
While OxLint doesn’t currently support a plugin system, it actively integrates rules from popular plugins like TypeScript, React, Jest, Unicorn, JSX-a11y, and Import. The team acknowledges the importance of plugins in the JavaScript ecosystem and is exploring a DSL-based plugin system.
OxLint’s release introduces a groundbreaking tool that not only surpasses ESLint in speed but also redefines the developer’s experience. Its focus on correctness, unmatched speed, and user-friendly design make it a compelling choice for JavaScript code checking. Whether you’re facing performance bottlenecks with ESLint or seeking a convenient, high-speed linting solution, OxLint is poised to make a significant impact.
Feel free to explore the OxLint project for more exciting features and enhancements. Happy coding!






