@etchteam/eslint-config
v2.2.9
Published
Etch's standard eslint config
Downloads
1,483
Keywords
Readme
@etchteam/eslint
The eslint config that we use at Etch
Install
npm i -D eslint prettier @etchteam/eslint-config
Usage
echo "module.exports = { extends: ['@etchteam'] };" > .eslintrc.cjs
With lint-staged
New project
Run the following:
npm i -D husky lint-staged
echo "module.exports = { '*.{ts,tsx,js,jsx,yml,yaml,json}': 'eslint --fix' };" > lint-staged.config.cjs
npx husky init
echo "npx --no-install -- lint-staged" > .husky/pre-commit
Existing project with husky and lint staged
Add the following to your lint-staged config:
'*.{ts,tsx,js,jsx,yml,yaml,json}': 'eslint --fix'
Usage with VSCode
New project with no VSCode config
Run the following:
mkdir .vscode
echo "{ \"editor.formatOnSave\": false, \"editor.codeActionsOnSave\": { \"source.fixAll.eslint\": \"explicit\" } }" > .vscode/settings.json
# The VSCode prettier extension doesn't read the eslint config, so specific
# prettier overrides need to go in a prettier config for format on save
echo "module.exports = { singleQuote: true };" > prettier.config.cjs
Exisiting project with VSCode config
Add the following to .vscode/settings.json
:
"editor.formatOnSave": false,
"editor.codeActionsOnSave": {
"source.fixAll.eslint": "explicit"
}
Run the following:
# The VSCode prettier extension doesn't read the eslint config, so specific
# prettier overrides need to go in a prettier config for format on save
echo "module.exports = { singleQuote: true };" > prettier.config.cjs