Special and Scoped Configurations

The 24 configurable artifacts cover the standard type-aware TypeScript path with optional React, Node.js, and AI concerns. Two complete named artifacts handle syntax-only and experimental compiler execution contracts. Vitest and Jest are composed as file-scoped policy instead of complete root configurations.

Syntax-only TypeScript

Use the syntax-only configuration when no project graph is available:

import { getSyntaxOnlyOxlintConfig } from "oxlint-config-setup";

export default getSyntaxOnlyOxlintConfig();

This is the only stable configuration that does not require the type-aware backend.

Vitest and Jest

Select one test owner deliberately:

import { getComposedOxlintConfig } from "oxlint-config-setup";

export default getComposedOxlintConfig({ scopes: ["vitest"] });

Use the jest scope for Jest. Both scopes match *.test.{ts,tsx} and __tests__/**/*.{ts,tsx}. They cannot be selected together because their shared APIs overlap.

React Compiler

Compiler diagnostics remain isolated from stable React defaults:

import { getExperimentalReactCompilerOxlintConfig } from "oxlint-config-setup";

export default getExperimentalReactCompilerOxlintConfig();

The native compiler rule starts as a warning and the export remains explicitly experimental.

Public JSON equivalents

Each complete named loader has a stable JSON subpath:

• oxlint-config-setup/json/typescript-syntax
• oxlint-config-setup/json/react-compiler

Vitest and Jest do not have static JSON equivalents because their policies are file-scoped fragments composed by the TypeScript loader.