Presets

What each preset owns — one plugin or framework integration per preset, nothing implied by another.

Every preset owns a disjoint slice of rules and stands alone — none of them extends another. rules merge key-by-key and plugins/jsPlugins union when you list several in your own extends array, so pick every preset your project needs; nothing comes along for free.

The one exception is base.

base

Assumes no runtime, no framework, no UI library — JS/TS correctness and security rules any project wants, a Node CLI and a React app alike. The only bundled preset in the package, since there’s no meaningful way to want half of it.

React

Five independent presets. react alone gets hooks correctness only — accessibility, performance, and React-Doctor’s broader catalog are each their own opt-in.

react-doctor’s rule catalog used to duplicate roughly 90 rules that react, react-perf, and jsx-a11y already cover under their own names — button-has-type, the entire jsx-a11y alt-text/aria/role catalog, all 4 react-perf prop-identity checks, and more. Those now live exclusively in the plugin they originate from; react-doctor only owns what’s genuinely original to it.

JSX runtime

react-in-jsx-scope depends on which JSX transform a project uses, so it’s a choice, not a default baked into react:

Pick exactly one.

Framework & Library Leaves

Each of these owns only its own slice of oxlint-plugin-react-doctor’s framework-specific rules — no react, react-a11y, react-perf, or react-doctor bundled in. Add those separately (you almost always want them, for anything that renders JSX).

Preact and React Native are runtime-ambiguous — pair either with jsx-runtime-automatic or jsx-runtime-classic depending on the project’s transform. Solid uses its own JSX transform (babel-preset-solid), not React’s, so neither jsx-runtime preset applies to it.

Opt-in Environment Presets

Not every project runs in Node or wants JSDoc type-annotation rules enforced (redundant once a project is on TypeScript, which base already assumes) — kept separate from base for that reason:

Testing

Split by test runner:

Storybook

Example: Next.js + TanStack, React Compiler on

import { defineConfig } from "oxlint";
import {
  base,
  react,
  reactA11y,
  reactDoctor,
  reactCompiler,
  jsxRuntimeAutomatic,
  nextjs,
  tanstackQuery,
  vitest,
} from "@zap-studio/oxlint";

export default defineConfig({
  extends: [
    base,
    react,
    reactA11y,
    reactDoctor,
    reactCompiler,
    jsxRuntimeAutomatic,
    nextjs,
    tanstackQuery,
    vitest,
  ],
});

Nine imports instead of one — the tradeoff for a preset stack that’s exactly what the project uses, nothing implied.

Where the Rules Come From

Every plugin named in the tables above — built-in or external — traces back to an upstream project or, for anti-slop, this repo directly. See Plugins for the source of each one and a link to the file where its rules are decided on or off.