@tim-code/eslint-config v1.1.2

eslint-config

npm install --save-dev @tim-code/eslint-config

Then in package.json:

  "eslintConfig": {
    "extends": [
      "@tim-code"
    ],
    "root": true,
    "ignorePatterns": []
  }

This assumes that code can use Node globals unless it is in a frontend directory. See below to change this.

Note that root and ignorePatterns are not required but root is useful to prevent ESLint from searching for more config files and ignorePatterns is often eventually needed to ignore files such as a build directory.

React

To fully support React/JSX, install:

npm install --save-dev eslint-plugin-react

Then in eslintConfig in package.json:

"extends": [
  "@tim-code",
  "plugin:react/recommended"
]

Because null is often used in React code, you may want to disable the warning about null:

"rules": [
  "no-restricted-syntax": "off"
]

Make src directory use "browser" globals instead of "node" globals

In eslintConfig in package.json:

"overrides": [
  {
    "files": [
      "src/**"
    ],
    "env": {
      "node": false,
      "browser": true
    }
  }
]

Instead, if there are no JS files in the project directory that require Node:

"env": {
  "node": false,
  "browser": true
}

Why not eslint-babel?

eslint-babel is a more flexible parser but using it is a bit more complex (requires configuration) and introduces another dependency.