Write Perfect Code with Standard and ESLint
summary
Clear, actionable claims: use Standard or ESLint to catch real bugs now, not just style debates. Concrete tooling: Standard CLI with 200+ pre-configured rules, --fix auto-fixes and standard-engine wrapper for shareable, non-editable configs. Surprising scale: Standard downloads ~1M/month and editor plugins exist. Concrete bug examples detected: assignment-in-condition, duplicate parameters, unreachable loop conditions, invalid typeof comparisons. Prettier handles only style, so keep a linter for correctness.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:13WRITE PERFECT CODE WITH STANDARD AND ESLINT Feross Aboukhadijeh
- 1:38A LINTER CATCHES BUGS
- 1:59What's a bug?
- 2:35BUGBEAR BUGABOO BOOGEYMAN
- 5:46ESLINT Catches programmer errors
- 8:27CATCH PROGRAMMER ERRORS Shorten the Feedback Loop
- 13:42standard JS
- 15:36BEWARE OF BIKESHEDDING
- 18:30PROGRAMMER ERRORS BEST PRACTICES STYLE ISSUES
- 22:08FINAL TIPS
related talks
35mYou Could Lint More
31mDevelopment Standards: A Step-by-Step Guide to Implementing Them Without Pain
24mStatic Analysis: Don't Fear the Linter!
14mGetting Started with JavaScript Linter | What Is Linter?
31mCode Style and Violence
36mEnforcing coding standards in a JS library
37mHow to stop writing buggy code
37mCoding Automation Lesson #1: Please Be Lazy