oxlint Rules Explorer

oxlint is a JavaScript and TypeScript linter written in Rust, developed as part of the oxc (Oxidation Compiler) project. It runs 50-100x faster than ESLint due to Rust's parallel processing and zero-cost abstractions. It covers a subset of the most impactful ESLint rules and is designed to complement (not immediately replace) ESLint.

oxlint is much faster but currently covers fewer rules than ESLint. ESLint has a rich plugin ecosystem (eslint-plugin-react, @typescript-eslint, etc.) that oxlint does not yet fully replicate. The recommended approach is to run oxlint first (for speed) and ESLint after (for plugin rules). Over time, oxlint will absorb more rules.

oxlint uses an .oxlintrc.json file (or oxlint key in package.json). The format is similar to ESLint's flat config: an object with a 'rules' key mapping rule names to 'error', 'warn', or 'off'. You can also add 'plugins', 'env', and 'globals' settings.

On large codebases, oxlint typically lints 50-100x faster than ESLint. For a 500K-line codebase, ESLint might take 60 seconds; oxlint finishes in under 1 second. This makes it ideal as a fast pre-commit check or CI gate before the full ESLint run.

Yes. oxlint supports TypeScript out of the box with no additional configuration. Run oxlint on .ts and .tsx files directly. TypeScript-specific rules (no-explicit-any, etc.) are included in the core rule set.

Install with: npm install oxlint. Run on a directory: npx oxlint src/. Use --fix to auto-fix fixable rules. Use --config .oxlintrc.json to specify a custom config file. You can also run it via the VSCode extension for inline diagnostics.