eslint-config-recommended
v4.1.0
Published
Pluggable ESLint configs for ECMAScript Next, Node.js and React Native that you can import, extend and override
Readme
Pluggable ESLint configs for ECMAScript Next, Node.js and React Native that you can import, extend and override
Usage
In your js project directory:
npm install --save-dev eslint-config-recommendedChoose the configs you want to include in your .eslintrc.yaml:
extends:
- recommended/esnext
- recommended/esnext/style-guide
- recommended/node
- recommended/node/style-guide
- recommended/react-native
- recommended/react-native/style-guideAlternatively, in your .eslintrc.js or .eslintrc.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:
To add a git-hook to your commits, consider using husky
npm install --save-dev huskyAnd in your package.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.
