Expo

Use Expo support from the main v2 package. Application projects no longer install a separate @santi020k/eslint-config-expo package.

Install

pnpmnpmYarnBun

bash

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

bash

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

bash

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

bash

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

Using Lite

The default install above remains recommended. If you use the manual-dependency lite package, install this framework config package too:

pnpmnpmYarnBun

bash

pnpm add -D @santi020k/eslint-config-lite @santi020k/eslint-config-expo eslint

bash

npm install -D @santi020k/eslint-config-lite @santi020k/eslint-config-expo eslint

bash

yarn add -D @santi020k/eslint-config-lite @santi020k/eslint-config-expo eslint

bash

bun add -d @santi020k/eslint-config-lite @santi020k/eslint-config-expo eslint

Configure

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

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

Most projects can also rely on auto-detection and use eslintConfig() with no framework object.

What It Adds

• Expo and React rules. React is included automatically.
• 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

• The internal package still exists in the monorepo for modular development and generated API docs.
• For the old multi-package installation model, see the v1 Expo guide.

Related Pages

• Installation
• Configuration
• v1 to v2 Migration