ESLint and Prettier Config for Yellow Card
MIT License
These are Yellow Card settings for ESLint and Prettier
You might like them - or you might not. Suggest a change and we can discuss as a team.
You can use eslint globally and/or locally per project.
It's usually best to install this locally once per project, that way you can have project specific settings as well as sync those settings with others working on your project via git.
I also install globally so that any project or rogue JS file I write will have linting and formatting applied without having to go through the setup. You might disagree and that is okay, just don't do it then 😃.
If you don't already have a package.json
file, create one with npm init
.
Then we need to install everything needed by the config:
npx install-peerdeps --dev @yellowcard/yellowcard-styling-config
You can see in your package.json there are now a big list of devDependencies.
Create a .eslintrc
file in the root of your project's directory (it should live where package.json does). Your .eslintrc
file should look like this:
{
"extends": [
"yellowcard-styling-config"
]
}
Tip: You can alternatively put this object in your package.json
under the property "eslintConfig":
. This makes one less file in your project.
"scripts": {
"lint": "eslint .",
"lint:fix": "eslint . --fix"
},
Now you can manually lint your code by running npm run lint
and fix all fixable issues with npm run lint:fix
. You probably want your editor to do this though.
To use from the CLI, you can now run eslint .
or configure your editor as we show next.
If you'd like to overwrite eslint or prettier settings, you can add the rules in your .eslintrc
file. The ESLint rules go directly under "rules"
while prettier options go under "prettier/prettier"
. Note that prettier rules overwrite anything in my config (trailing comma, and single quote), so you'll need to include those as well.
{
"extends": [
"yellowcard-styling-config"
],
"rules": {
"no-console": 2,
"prettier/prettier": [
"error",
{
"trailingComma": "es5",
"singleQuote": true,
"printWidth": 120,
"tabWidth": 8,
}
]
}
}
You should read this entire thing. Serious!
Once you have done one, or both, of the above installs. You probably want your editor to lint and fix for you. Here are the instructions for VS Code:
Code/File
→ Preferences
→ Settings
. It's easier to enter these settings while editing the settings.json
file, so click the {}
icon in the top right corner: // These are all my auto-save configs
"editor.formatOnSave": true,
// turn it off for JS and JSX, we will do this via eslint
"[javascript]": {
"editor.formatOnSave": false
},
"[javascriptreact]": {
"editor.formatOnSave": false
},
// tell the ESLint plugin to run on save
"eslint.autoFixOnSave": true,
// Optional BUT IMPORTANT: If you have the prettier extension enabled for other languages like CSS and HTML, turn it off for JS since we are doing it through Eslint already
"prettier.disableLanguages": ["javascript", "javascriptreact"],
start fresh. Sometimes global modules can goof you up. This will remove them all.
npm remove --global yellowcard-styling-config babel-eslint eslint eslint-config-prettier eslint-config-airbnb eslint-plugin-html eslint-plugin-prettier eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-react prettier eslint-plugin-react-hooks
To do the above for local, omit the --global
flag.
Then if you are using a local install, remove your package-lock.json
file and delete the node_modules/
directory.
Then follow the above instructions again.