ESLint

How CodeRabbit runs ESLint to lint JavaScript, TypeScript, and framework files on every pull request — including supported plugins, sandboxed execution, and skip conditions.

ESLint is a linter for JavaScript, TypeScript, JSX, TSX, CSS, etc. CodeRabbit runs ESLint automatically on every pull request in a secure sandbox, using your repository’s own ESLint configuration when present and posting results as inline review comments.

Files

ESLint will run on package.json and files with the following extensions: .js, .ts, .cjs, .mjs, .d.cts, .d.mts, .jsx, .tsx, .css, .vue, .svelte, .astro, .graphql, .gql, .mdx

Configuration

enabled · boolean · default: true

Enable ESLint

config_file · string

Optional path to an ESLint configuration file relative to the repository. When set, this configuration is used for every file instead of discovering ESLint configurations recursively.

e18e · object

@e18e/eslint-plugin modernization, performance, and dependency replacement checks.

Show options

e18e.enabled · boolean · default: true

Enable @e18e/eslint-plugin: Detects dependencies with modern replacements, flags unmaintained packages, and suggests native API alternatives or lighter replacements

Version: v0.8.1

.coderabbit.yaml

.coderabbit.yaml

reviews:
  tools:
    eslint:
      enabled: true
      config_file: "eslint.config.js"
      e18e:
        enabled: true

Web UI

In your organization or repository settings, go to Reviews → Tools and turn the tool on or off with its toggle. To change its other settings, click the settings icon next to the toggle.

The e18e.enabled setting controls CodeRabbit-managed @e18e/eslint-plugin checks. The managed overlay is temporarily disabled at runtime while an installation hotfix is active, so changing this setting currently has no effect. When the overlay is active, the Chill profile reports its recommended rules and e18e/ban-dependencies as warnings, while the Assertive profile uses the recommended severities and reports e18e/ban-dependencies as an error. CodeRabbit does not add the managed overlay when your ESLint configuration already references e18e.

• ESLint configuration is read from the repository and is used as is. If no applicable ESLint configuration file is found for a changed file, CodeRabbit skips ESLint for that file.

• Please ensure that all ESLint dependencies are defined in your package.json file(s).

• Yarn and PNPM workspaces are supported.

• Private ESLint plugins or configurations are not supported at the moment. Please reach out to support if you would like us to add support for this.

• For @typescript-eslint, linting with type information is not supported at the moment. The type checking rules are disabled.

• For eslint-plugin-import, the following rules are disabled:

  • import/no-unresolved

• For the eslint-plugin-n, the following rules are disabled:

  • n/no-missing-import
  • n/no-missing-require

• For the eslint-plugin-node, the following rules are disabled:

  • node/no-missing-import
  • node/no-missing-require

Configuration file discovery

CodeRabbit searches the repository recursively for ESLint configuration files. It supports both flat-config and legacy-config filenames:

• Flat config: eslint.config.js, eslint.config.mjs, eslint.config.cjs, eslint.config.ts, eslint.config.mts, and eslint.config.cts
• Legacy config: .eslintrc, .eslintrc.js, .eslintrc.cjs, .eslintrc.json, .eslintrc.yml, and .eslintrc.yaml

For each changed file, CodeRabbit uses the closest discovered ESLint config in that file’s directory ancestry. For example, foo/bar/.eslintrc.js is automatically used for files under foo/bar/ and its subdirectories, but not for files outside foo/bar/.

CodeRabbit does not use an eslintConfig field in package.json as a configuration source. Use one of the supported configuration files instead.

Setting config_file replaces this discovery. CodeRabbit rejects URLs, absolute paths, paths containing .., and paths that do not exist.

Security policy and restrictions

ESLint runs in a sandbox. CodeRabbit scans ESLint config files before any npm/yarn/pnpm installs and only permits a curated allow-list of plugins.

• CodeRabbit extracts referenced plugins from configs (the plugins array, extends: "plugin:...", eslint-plugin-... mentions).
• If any plugin outside the allow-list is referenced, CodeRabbit skips ESLint for the run.
• CodeRabbit does not install or execute arbitrary third-party plugins from the repository.

The following plugins are currently allowed, grouped by category:

Category	Plugins
TypeScript / Stylistic	@typescript-eslint, @stylistic
Import / Module	import, import-x, simple-import-sort, unused-imports, n, node
React ecosystem	react, react-hooks, react-native, react-refresh, jsx-a11y, next
Testing	jest, jest-dom, vitest, testing-library, cypress, playwright, mocha
Frameworks	vue, nuxt, angular, @angular-eslint, @angular-eslint/template, @nx, svelte, astro, solid, qwik, turbo, hydrogen, storybook
Code quality	sonarjs, security, unicorn, promise, regexp, compat, jsdoc, deprecation, lodash, boundaries, perfectionist, eslint-comments, e18e
Formatting	prettier, tailwindcss
Other	mdx

When CodeRabbit skips ESLint

CodeRabbit will skip running ESLint when:

• The config references a plugin not in the allow-list.
• The config can’t be parsed or is otherwise unsafe.
• config_file is not a repository-relative path or does not exist.
• No package.json exists at the repository root.
• No relevant package.json declares ESLint as a dependency or development dependency.
• No applicable ESLint configuration is found for a changed file.
• Required dependencies cannot be installed or resolved in the sandbox.

Ignored rules

CodeRabbit filters out findings for the following rule IDs, including rule IDs with a namespace that end with the same value:

• camelcase
• comma-dangle
• comma-spacing
• func-style
• indent
• linebreak-style
• no-trailing-spaces
• no-use-before-define
• no-var
• quote-props
• quotes
• retayl/no-hardcoded-colors
• ts/no-unsafe-call
• vars-on-top

What’s next

All supported tools

Browse the complete list of linters, security analyzers, and CI/CD integrations available in CodeRabbit.

Tools reference

Explore detailed specifications and capabilities of all available CodeRabbit tools.

Configuration reference

Full reference for all available options, including how to enable, disable, and tune individual tools.