Oxlint best practices

Use when linting JavaScript or TypeScript projects with Oxlint, configuring .oxlintrc.json or oxlint.config.ts, or migrating from ESLint.

Mental model

• Treat Oxlint as a fast, correctness-focused linter with broad ESLint ecosystem compatibility, not as a drop-in assumption that every ESLint edge case behaves identically.
• Start with the default high-signal rules, then expand rule coverage deliberately instead of enabling everything blindly.
• Keep lint policy explicit in config rather than scattering behavior across CI flags and editor-only setup.

Setup and config

• Commit a shared Oxlint config so local runs, editors, and CI agree.
• Keep ignore patterns deliberate; ignored paths should usually be generated output, vendor code, or files the project truly does not own.
• Prefer stable repo-level scripts such as lint and lint:fix over ad hoc CLI invocation.

Vite+ exception