2
When we perform eslint --init
, we first come across the following question:
I performed two tests, one selecting "To check syntax and find problems" and other using "To check syntax, find problems, and enforce code style", for this last option I still chose the Style Guide Standard. In the final tests I obtained the same behavior for stylization and linting.
My question is: because it is using prettier
with eslint-config-prettier
and eslint-plugin-prettier
, still it is recommended to select "To check syntax, find problems, and enforce code style"? From what I could understand analyzing the project, when using Prettier this would be unnecessary since the Prettier by default is already adhering to Style Guide Standard, but I’m still not sure if this reasoning is correct.
My file .eslintrc.json
:
{
"env": {
"es6": true,
"node": true
},
"extends": [
"standard",
"prettier"
],
"globals": {
"Atomics": "readonly",
"SharedArrayBuffer": "readonly"
},
"parser": "babel-eslint",
"parserOptions": {
"ecmaVersion": 2018,
"sourceType": "module"
},
"plugins": [
"prettier"
],
"rules": {
"prettier/prettier": "error"
}
}