eslint-config-expo

Install

1. Install Eslint on your projet

yarn add --dev eslint @eslint/js

2. Install config

yarn add --dev @nodstudio/eslint-config-expo

3. Add config to yours

import nodStudioConfigExpo from "@nodstudio/eslint-config-expo";

export default [
    // ...
    ...nodStudioConfigExpo
];

4. (Optional) For a better experience, please use @nodstudio/prettier-config-expo

Usage

Imports

The goal is to force a file structure logic where low-levels components can't import high-levels components.

| folder | can't import from | |:---:|:---:| | @design/**/*@/design/**/*design/**/*src/design/**/* | @containers/**/*@/containers/**/*containers/**/*src/containers/**/*@components/**/*@/components/**/*components/**/*src/components/**/* | | @components/**/*@/components/**/*components/**/*src/components/**/* | @containers/**/*@/containers/**/*containers/**/*src/containers/**/* |

Examples

With new expo file structure : .
├── app
├── assets
├── components (can't import from ./containers)
├── containers
├── db
├── design (can't import from ./components or ./containers)
├── doc
├── enums
├── game
├── models
├── scripts
└── utils

With old expo file structure :
.
├── assets
├── doc
├── scripts
└── src
    ├── app
    ├── components (can't import from src/containers)
    ├── containers
    ├── db
    ├── design (can't import from src/components or src/containers)
    ├── enums
    ├── game
    ├── models
    └── utils