ESLint
The pluggable JavaScript linter that defined what a code style violation is.
why this verdict
Keep it for the workflow, not the AI
Biome and Oxlint cover the headline feature free, and the workflow around it is why you would still open this.
- A named launch, not a vibe named, unlinked
- AI reviewers catching semantic bugs no static rule could express, plus Rust linters taking the speed argument. Anthropic, June 18, 2025 — no announcement link recorded yet.
- How much of the job it covers headline only editorial call
- The headline feature, but not the workflow, data or integrations around it.
- Is there a free way to do it? yes
- 3 of 3 listed replacements have a usable free tier: Biome, Oxlint and deno lint.
- What the call is worth nothing to cancel
- No paid entry tier tracked, so there is no subscription to cancel.
- Threatened by
- Anthropic
- Since
- June 18, 2025
- List price
- free
- Per year
- —
The backstory
ESLint has been the arbiter of JavaScript correctness and style for a decade, with a plugin ecosystem covering every framework. It is squeezed from two directions at once. Above it, AI code review comments on intent and catches bugs no rule could encode. Below it, Biome and Oxlint do the mechanical checks in Rust an order of magnitude faster. ESLint keeps its enormous rule ecosystem and its role as the thing CI actually enforces, but the flat-config migration cost teams goodwill at the worst possible moment.
Escape hatches
Rust linter and formatter in a single fast binary
biomejs.dev open_in_newExtremely fast Rust-based linter, largely ESLint-compatible
oxc.rs open_in_newBuilt into the Deno toolchain with no configuration
docs.deno.com open_in_new3 of 3 replacements have a usable free tier.
