Use project scripts when they exist because they may include workspace filters, plugin flags, or warning gates.

Common Commands

bun run lint
bun run lint:fix
bun run fmt
bun run fmt:check

Direct commands when no script exists:

oxlint
oxlint --fix
oxlint --type-aware
oxlint --deny-warnings
oxfmt --check .
oxfmt --write .

Prefer checking touched files when the project supports it. Run the full project gate before completion.

Oxlint Configuration

Oxlint supports .oxlintrc.json and oxlint.config.ts.

import { defineConfig } from "oxlint";

export default defineConfig({
  options: {
    typeAware: true,
  },
  rules: {
    "typescript/consistent-return": "error",
  },
});

Use --type-aware or options.typeAware when rules need TypeScript semantic information.

Fixing Diagnostics

Read the rule name and message.
Fix the underlying issue, not just the syntax.
Use --fix for safe fixes.
Avoid unsafe or dangerous fixes unless the user explicitly approves them.
Use ignore comments only for confirmed false positives, with a reason.

// oxlint-ignore-next-line no-console -- CLI output is the command result
console.log(result);

CI and Warning Gates

If the project treats warnings as failures, use one of:

oxlint --deny-warnings
oxlint --max-warnings 0

Do not claim lint passed if warnings remain and the repo policy treats warnings as blocking.

Monorepo Guidance

Run commands from the workspace root unless package scripts document otherwise.
Watch for nested configs; Oxlint can resolve nested configuration files.
Use package filters only when the repo's scripts support them.
Re-run the aggregate verify command before delivery.

Common Mistakes

Running npx oxlint when the repo has a stricter bun run lint script.
Suppressing diagnostics before understanding them.
Formatting the whole repository for a narrow change.
Forgetting type-aware linting when the config expects it.
Treating warnings as acceptable in repositories with zero-warning policy.

oxlint-oxfmt

Oxlint and Oxfmt

Detection