React

Use React support from the lean v3 composer. Install the @santi020k/eslint-config-react package.

Install

pnpmnpmYarnBun

bash

pnpm add -D @santi020k/eslint-config-basic @santi020k/eslint-config-react eslint

bash

npm install -D @santi020k/eslint-config-basic @santi020k/eslint-config-react eslint

bash

yarn add -D @santi020k/eslint-config-basic @santi020k/eslint-config-react eslint

bash

bun add -d @santi020k/eslint-config-basic @santi020k/eslint-config-react eslint

Configure

import { defineConfig } from '@santi020k/eslint-config-basic'

export default await defineConfig({
  frameworks: {
    react: true
  },
  typescript: true
})

With the required config packages installed, the one-line recommended entry auto-detects the framework; custom configs can use defineConfig() without a frameworks object.

What It Adds

• React component and Hooks rules.
• Composition through the same @santi020k/eslint-config-basic entry point as every other framework.
• Compatibility with advanced overrides if you pass a custom config array or factory instead of true.

Notes

• This framework package is a public, optional dependency in v3; the basic composer loads it only when enabled.

• @eslint-react/no-nested-component-definitions has no component-slot option. Hoist a slot component when it does not need owner state. If a library API requires an inline component map that intentionally captures that state, keep the exception to the adapter file instead of disabling the rule for the application:

  export default await defineConfig({}, {
    files: ['src/components/ui/calendar.tsx'],
    rules: {
      '@eslint-react/no-nested-component-definitions': 'off'
    }
  })

• For the archived v1 setup, see the v1 React guide.

Related Pages

• Installation
• Configuration
• v2 to v3 Migration