wtf is eslint?

ESLint is a quality-checking tool for JavaScript code. It reads through your code and finds patterns that might indicate bugs, inconsistencies, or style violations, then reports them back to you. Think of it like a spell-checker for your JavaScript, except it's looking for logical problems and style issues instead of spelling mistakes. The tool works by reading your JavaScript file, breaking it down into its component parts (what developers call an Abstract Syntax Tree), and then checking those components against a set of rules you define. You create a simple configuration file that tells ESLint which patterns to look for and how strict to be about each one. For example, you might say "always use semicolons at the end of statements" or "always use double quotes instead of single quotes." Each rule can be turned off entirely, set as a warning, or set as a hard error that will fail your code review. Developers and teams use ESLint to keep their JavaScript codebases clean and consistent. A startup building a web app might run ESLint before merging code to catch common mistakes. A large company might use it to enforce a consistent coding style across hundreds of engineers. It catches things like unused variables, confusing logic patterns, and formatting inconsistencies that would otherwise require tedious manual code review. What makes this tool different from older alternatives is that it's completely customizable, you can write your own rules and add them at runtime, and every built-in rule is already a plugin. That means you're not locked into a fixed set of checks, you can extend it to match exactly what your team cares about. The README does note that it's slower than some alternatives because of how it parses code, but it's still fast enough for everyday use, and if you're using multiple checkers together, consolidating to just ESLint is actually faster.