Oxc

Oxc — suite of JS tooling (parser, linter, formatter) in Rust.

Build ToolsModerate

Stack Components

ToolchainOxc

Why

50-100x faster than JS-based tools, ESLint-compatible linter, Prettier-like formatter. Vite 5 builds 10-20x faster than Webpack (esbuild + Rollup core).

Turborepo and Nx cut monorepo CI times by 60-80% via remote caching and task parallelization.

When

Use for large JS/TS codebases. Avoid for projects needing specific ESLint plugins.

How

1. npm install oxlint 2. npx oxlint . 3. Configure .oxlintrc.json 4. Integrate with CI 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

// .oxlintrc.json { "rules": { "no-unused-vars": "error", "eqeqeq": "error" } }

Common Problems

⚠Rule coverage — check oxlint rule list vs ESLint
⚠Config format — use eslint-compatible config
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use oxlint for fast CI linting
✓Keep ESLint for type-aware rules
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Oxc and what projects is it for?

Oxc — suite of JS tooling (parser, linter, formatter) in Rust. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Oxc in 10 minutes?

Two steps: (1) npm install oxlint; (2) npx oxlint .. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Oxc and how do I avoid it?

The most common pitfall is: Rule coverage — check oxlint rule list vs ESLint. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Oxc?

Best practices for Oxc include: Use oxlint for fast CI linting; Keep ESLint for type-aware rules; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use oxlint for fast CI linting" — should be set up at project init to avoid costly rework later.

When should I NOT choose Oxc?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Oxc shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.