Which Linting Tool?: Explained

Which Linting Tool? Explained

Answer a few questions about how much config you want, how much speed matters, whether you want formatting bundled in, and how large your plugin needs are to choose between ESLint, Biome, Oxlint, and StandardJS.

A linter flags mistakes and bad patterns before they run. The choice turns on three dials: how much you want to configure, how fast it must run, and whether you want a formatter bundled in. Modern Rust-based tools are far faster but younger; ESLint is slower but has every plugin. Answer below to get a recommendation, ranked against the alternatives.

Decision guide · 4 options

The options

ESLint

The standard, with the largest plugin and rule ecosystem.

Teams that need custom rules, framework plugins (Next.js, React, Vue), and a battle-tested config they already know.

Biome

A fast, all-in-one Rust tool: linter and formatter in one.

Projects that want one tool instead of two, near-instant runs, and sensible defaults with a single config.

Oxlint

A very fast Rust linter focused on rules and ease of adoption.

Large codebases that want to drop in a blindingly fast linter alongside or ahead of ESLint.

StandardJS

An opinionated style with zero config and no semicolons.

Small projects or solo developers who want one accepted style with nothing to debate and nothing to configure.

Which one fits you?

Answer a few questions to get a recommendation.

Question 1 of 4