mirror of
https://github.com/goldbergyoni/nodebestpractices.git
synced 2025-11-01 18:46:54 +08:00
Update README.md
This commit is contained in:
@ -221,7 +221,7 @@
|
||||
|
||||
## ![✔] 3.1 Use ESLint
|
||||
|
||||
**TL;DR:** [ESLint](https://eslint.org) is the de-facto standard for checking possible code errors and fixing code style, not only to identify nitty-gritty spacing issues but also to detect serious code anti-patterns like developers throwing errors without classification. Though ESLint can automatically fix code styles, other tools are more powerful in formatting the result and can work in conjuction with ESLint
|
||||
**TL;DR:** [ESLint](https://eslint.org) is the de-facto standard for checking possible code errors and fixing code style, not only to identify nitty-gritty spacing issues but also to detect serious code anti-patterns like developers throwing errors without classification. Though ESLint can automatically fix code styles, other tools are more powerful in formatting the result and work in conjuction with ESLint
|
||||
|
||||
**Otherwise:** Developers will focus on tedious spacing and line-width concerns and time might be wasted overthinking about the project's code style.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user