eslint-config-recommended

Pluggable ESLint configs for ECMAScript Next, Node.js and React Native that you can import, extend and override

!Join the chat at https://gitter.im/kunalgolani/eslint-config gitter-imggitter-url !npm versionversion-imgnpm-url !npm downloadsdownloads-imgnpm-url !GitHub issuesissues-imgissues-url !Depsdeps-imgdeps-url !Dev Depsdevdeps-imgdeps-url

Usage

In your js project directory: ```shell npm install --save-dev eslint-config-recommended ``` Choose the configs you want to include in your .eslintrc.yaml: ```yaml extends: - recommended/esnext - recommended/esnext/style-guide - recommended/node - recommended/node/style-guide - recommended/react-native - recommended/react-native/style-guide ``` Alternatively, in your .eslintrc.js or .eslintrc.json: ```json { "extends": "esnext", "esnext/style-guide", "node", "node/style-guide", "react-native", "react-native/style-guide" } ``` node and react-native extend esnext node/style-guide and react-native/style-guide extend esnext/style-guide If you don't need all these configs, you can also install them individually:

• ESNext

• Node.js

• React Native

To add a git-hook to your commits, consider using husky ```shell npm install --save-dev husky ``` And in your package.json: ```json "scripts": {

"precommit": "eslint ."

} ``` ---

Config

These configs are biased and opinionated, and err on the side of too many rules instead of too few. Think of them as a superset of your repo's lint config, and discard what you don't like in them. It's easy to override and disable the rules you find inconvenient.

• ESNext

• ESNext Style Guide

• Node.js

• Node.js Style Guide

• React Native

• React Native Style Guide