Ignore files

Large repositories contain files that should not be linted, such as build output, vendored code, snapshots, or generated artifacts. Oxlint provides a predictable ignore model that works well in monorepos and CI.

TIP

It is strongly recommended to use "ignorePatterns" in your Oxlint config file (.oxlintrc.json or oxlint.config.ts) for ignoring files rather than a separate ignore file. This ensures that every developer will have the same ignores across all tools and commands running Oxlint, especially IDE/editor integrations. It also keeps your configuration centralized to one file.

Default ignores

Oxlint automatically ignores:

• .git directories
• Minified files containing .min., -min., or _min. in the file name
• Files matched by .gitignore (global gitignore files are not respected)

Hidden files are not automatically ignored.

ignorePatterns

The recommended approach is to define ignores in your config file using ignorePatterns. This keeps ignores close to the configuration they belong to and works naturally with nested configs.

Patterns are resolved relative to the configuration file.

.oxlintrc.json

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "ignorePatterns": ["dist/**", "coverage/**", "vendor/**", "test/snapshots/**"]
}
``````ts [oxlint.config.ts]
import { defineConfig } from "oxlint";

export default defineConfig({
  ignorePatterns: ["dist/**", "coverage/**", "vendor/**", "test/snapshots/**"],
});
``````bash
oxlint --ignore-path path/to/ignorefile
``````bash
oxlint --ignore-pattern 'dist/**' --ignore-pattern 'coverage/**'
``````json [.oxlintrc.json]
{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "ignorePatterns": ["build/**/*", "!build/keep.js"]
}
``````ts [oxlint.config.ts]
import { defineConfig } from "oxlint";

export default defineConfig({
  ignorePatterns: ["build/**/*", "!build/keep.js"],
});
``````bash
oxlint --no-ignore