A good project is a project with a consistent code base. The #1 Editorconfig issue already takes care of half the problem, standardising the editor configurations.
To go even further, a good option is to install XO and let it do the linting for us. I'm always a big fan of smart defaults than configuration. And XO excels at it,
What's good
Beautiful output.
Zero-config, but configurable when needed.
Enforces readable code, because you read more code than you write.
No need to specify file paths to lint as it lints all JS files except for commonly ignored paths.
Config overrides per files/globs. (ESLint doesn't support this)
Includes many useful ESLint plugins, like unicorn, import, ava, and more.
Super simple to add XO to a project with $ xo --init.
Fix many issues automagically with $ xo --fix.
Open all files with errors at the correct line in your editor with $ xo --open.
Specify indent and semicolon preferences easily without messing with the rule config.
A good project is a project with a consistent code base. The #1 Editorconfig issue already takes care of half the problem, standardising the editor configurations.
To go even further, a good option is to install XO and let it do the linting for us. I'm always a big fan of smart defaults than configuration. And XO excels at it,
What's good