Post

We're thrilled to announce the first stable release of Oxlint - version 1.0! Our Rust-powered JavaScript/TypeScript linter delivers 50~100x faster performance than ESLint with 500+ rules and zero configuration required. Time to give it a try! voidzero.dev/posts/announ...

voidzero.devAnnouncing Oxlint 1.0The first stable version of Oxlint, a fast & easy-to-use Rust-powered linter for JavaScript and TypeScript, is out. Learn about its 50~100x speed advantage over ESLint, support for 500+ rules, real-wo...

61 reposts301 likes

With more than 5,200 early adopters, Oxlint already made impact in real-world projects, including major companies: * Shopify uses Oxlint to lint their admin console * Airbnb runs multi-file rules on >126k files in just 7s * Mercedes-Benz switched and saw up to 97% speedup

I swapped out ESLint for Oxlint close to a year ago to run on a codebase of ~75,000 lines of typescript. I used ESLint for years before that. Oxlint does the job and can attest to the 50x-100x performance boost. Thank you VoidZero and Boshen, and congratulations on the 1.0 release!

> It is recommended to run oxlint && eslint to benefit from Oxlint's faster feedback cycle. Won't this essentially mean that linting will be slower now, because it first runs oxlint and then the existing eslint setup? Or does disabling the overlapping rules result in a total speedup?

It's been such a game changer for us! ESlint took up to 11 minutes to run on all packages in our monorepo, and oxlint does all of it in under 1 second! Now we have type aware linting set up using typescript-eslint (thanks @joshuakgoldberg.com!) and it only takes around 6 minutes.

So we've increased the number of linting rules, added type aware linting, and the overall time has gone down! We run oxlint first, so if there are errors from that the CI job fails and skips the ESlint run.