Why oxfmt and oxlint Are Redefining Frontend Toolchains with 30‑50× Speed Gains

oxfmt and oxlint Overview

oxfmt and oxlint are core components of the OXC toolchain from VoidZero. They target formatting and linting performance for JavaScript/TypeScript projects.

Adoption Metrics

oxfmt ~510,000 weekly npm downloads within two months of release.

oxlint ~1,250,000 weekly npm downloads within one year.

oxfmt – High‑Performance Formatter

Problem: In large monorepos or CI pipelines, Prettier can take dozens of seconds per run, slowing pre‑commit hooks and pipeline stages.

Performance: Benchmarks (no cache, first run) show oxfmt formats code ~30× faster than Prettier and faster than Biome.

Technical characteristics:

API and configuration compatible with Prettier; can replace Prettier without code changes.

Focuses solely on code style; no semantic analysis.

Implemented in Rust, providing stable performance and lower memory footprint.

Built‑in import sorting and Tailwind CSS class ordering.

Migration: Install via npm ( npm i -D oxfmt) and replace Prettier commands (e.g., oxfmt . --write). No additional configuration required for most projects.

oxlint – Fast ESLint Alternative

Problem: ESLint runs single‑threaded in Node.js, leading to multi‑second linting times on large codebases.

Performance: oxlint achieves tens‑of‑times speedup; multi‑threaded runs that previously took dozens of seconds complete in under one second.

Key implementation details:

Rust implementation enables native parallelism.

Unified AST and parsing pipeline eliminates redundant work.

Parallel execution across CPU cores.

Compatibility:

Rule semantics align with ESLint; supports standard ESLint comments.

Can be introduced gradually; projects can run both tools during migration.

Usage example:

npm i -D oxlint
oxlint src/**/*.ts --fix

Strategic Direction

Both tools illustrate VoidZero’s strategy of rewriting performance‑critical front‑end tooling in Rust, focusing on high‑frequency operations such as linting and formatting rather than creating new frameworks.

When speed improvements reach 30×–50×, the decision shifts from “whether to migrate” to “when to migrate.”

Current Status

oxlint is production‑ready as an ESLint replacement.

oxfmt continues rapid development with clear performance benefits.