@jwalsh/eslint-config-recommended
v1.5.2
Published
Pluggable ESLint configs for ECMAScript Next, Node.js and React Native that you can import, extend and override
Downloads
12
Maintainers
Readme
eslint-config
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-recommended
Choose 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-guide
Alternatively, in your .eslintrc.js
or .eslintrc.json
:
{
"extends": [
"recommended/esnext",
"recommended/esnext/style-guide",
"recommended/node",
"recommended/node/style-guide",
"recommended/react-native",
"recommended/react-native/style-guide"
]
}
recommended/node
and recommended/react-native
extend recommended/esnext
recommended/node/style-guide
and recommended/react-native/style-guide
extend recommended/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 husky
And 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.