From the course: Node.js: Testing and Code Quality

Unlock the full course today

Join today to access over 24,700 courses taught by industry experts.

Standardizing with EditorConfig

Standardizing with EditorConfig

From the course: Node.js: Testing and Code Quality

Start my 1-month free trial Buy for my team

Standardizing with EditorConfig

“

- [Instructor] So far, we've been discussing concepts and terms. It's time to start cleaning up our code base and find errors using linting. In this chapter, we're going to start by standardizing text editor configurations. We'll add support for the standard to both our project and to VS Code. Once that's in place, we'll start comparing linters to see the advantages of each. With an informed decision, we'll install a linter that should address our needs. We'll step through how to create to the linters configuration then extend an existing shared linter configuration to save time. Then, we'll lint the entire code base and filter the results to be actionable. Finally, we'll set up VS Code to clean code and highlight linter errors. A developers preferred code editor is a badge of honor, and typically a passionate decision. With such a variety of options, how can you maintain coding styles across multiple editors with…

Contents