Linting is the automated process of analyzing code for potential errors, style inconsistencies, and problematic patterns. A linter scans your code and flags issues — unused variables, inconsistent formatting, potential bugs — before they cause problems. For vibe coders, linters catch mistakes in AI-generated code automatically.
Linters are your code's spell checker. They catch small mistakes that would otherwise accumulate into confusing, hard-to-maintain codebases.
| Category | Examples |
|---|---|
| Errors | Unused variables, unreachable code |
| Style | Inconsistent quotes, missing semicolons |
| Best practices | Console.log left in code, any type usage |
| Potential bugs | Equality with == instead of === |
| Linter | Speed | Notes |
|---|---|---|
| Biome | Fastest | Linter + formatter in one tool |
| ESLint | Standard | Most plugins and configurations |
| Prettier | Fast | Formatter only (pairs with ESLint) |
AI code usually follows best practices, but linters still catch:
npm install --save-dev @biomejs/biomeConfigure your editor to auto-fix lint issues on save. This means: