oxlint

A Rust-based JavaScript and TypeScript linter from the Oxc toolchain. 50–100x faster than ESLint, zero configuration required to start, built-in auto-fix, and a growing set of ESLint-compatible rules.

What is oxlint?

oxlint is a JavaScript and TypeScript linter written in Rust, developed as part of the Oxc (JavaScript Oxidation Compiler) project. It was designed from the ground up to be extremely fast by leveraging Rust's memory safety and parallel processing capabilities. On large codebases oxlint consistently benchmarks 50–100x faster than ESLint, often completing in milliseconds rather than seconds.

oxlint requires zero configuration to start — just point it at a directory and it immediately catches common correctness errors, suspicious patterns, and style issues. It supports JSX and TSX, has a built-in --fix flag, and is designed to be run alongside or as a replacement for ESLint as its rule coverage grows. The official documentation is at oxc.rs.

Key Features

• Written in Rust — delivers 50–100x speed improvements over ESLint; large monorepos lint in milliseconds
• Zero config to start — run npx oxlint . with no config file required; sensible defaults out of the box
• ESLint-compatible rules — covers a growing subset of ESLint core rules with the same names and semantics
• Built-in fix support — --fix flag auto-corrects fixable issues without extra plugins
• JSX and TSX support — understands React syntax and TypeScript generics natively
• Rule categories — correctness, pedantic, suspicious, restriction, and nursery categories for granular control
• Part of Oxc toolchain — integrates with oxc-parser, oxc-resolver, and other Oxc tools for a unified fast pipeline
• Run alongside ESLint — no forced migration; use oxlint as a fast first pass and ESLint for plugin-specific rules

Installation

# Run oxlint without installing (one-shot check)
npx oxlint@latest .

# Add oxlint as a dev dependency
npm add -D oxlint

# Lint the current directory
npx oxlint .

# Lint and auto-fix fixable issues
npx oxlint --fix .

# Lint a specific file or glob
npx oxlint src/

# Lint with a specific rule category enabled
npx oxlint --deny correctness .

Adding to package.json Scripts

The simplest integration is to add lint scripts to your package.json. oxlint exits with a non-zero code on errors, making it immediately usable in CI.

// package.json — add a lint script
{
  "scripts": {
    "lint": "oxlint .",
    "lint:fix": "oxlint --fix ."
  },
  "devDependencies": {
    "oxlint": "^0.4.0"
  }
}

GitHub Actions CI Integration

oxlint fits naturally into any CI workflow. Below is a minimal GitHub Actions example that lints on every push and pull request.

# .github/workflows/lint.yml
name: Lint

on: [push, pull_request]

jobs:
  oxlint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - run: npx oxlint .

Migrating from ESLint

The recommended migration strategy is incremental: run oxlint alongside ESLint first, identify overlapping rules, then progressively reduce ESLint's scope. This is zero-risk and immediately speeds up your CI feedback loop.

# Step 1 — run oxlint alongside ESLint (zero risk)
# oxlint catches issues ESLint misses at 50-100x the speed

# Step 2 — disable rules in ESLint that oxlint now covers
# oxlint outputs a list of covered rules:
npx oxlint --rules

# Step 3 — once confident, remove ESLint entirely
npm remove eslint eslint-config-* eslint-plugin-*
npm add -D oxlint

oxlint vs ESLint

Pros and Cons