JSPM

eslint-config-expo

6.0.0-rc.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 447455
  • Score
    100M100P100Q166895F
  • License MIT

Shared ESLint configs for Expo

Package Exports

  • eslint-config-expo

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-config-expo) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-config-expo

Shared ESLint configs for Expo's JS.

Installation

yarn add --dev eslint-config-expo

You will also need to install eslint and prettier:

yarn add --dev eslint prettier

Usage

Import this config into your own ESLint configuration using the extends option. ESLint checks both package.json and .eslintrc.* files for its configuration:

package.json

{
  "eslintConfig": {
    "extends": "expo"
  }
}

.eslintrc.js

module.exports = {
  extends: 'expo',
};

Support for Different Platforms

There are several configs for different platforms. They are:

  • expo: the basic config for JavaScript projects for which there isn't a more specific config
  • expo/native: the config for React Native projects, including Expo projects, with support for React and JSX
  • expo/web: the config for code that runs in web browsers, with support for React and JSX
  • expo/node: the config for code that runs in Node

For an Expo project, your configuration might look like this:

"eslintConfig": {
  "extends": "expo/native"
}

You also can extend multiple configs, which is useful for projects that span several platforms:

"eslintConfig": {
  "extends": ["expo/node", "expo/web"]
}