tkh44/standard

JavaScript Standard Style is a linter, a tool that checks your code and flags style problems, that removes all the decision-making about how to format JavaScript. Instead of debating whether to use tabs or spaces, semicolons or no semicolons, you just install this tool and it enforces one consistent style across your entire project automatically. The practical benefit is speed and simplicity. When you add this to your project, you don't have to write configuration files, argue about style in code reviews, or teach new teammates your rules. You run standard (either from the command line or as part of your test suite), it scans your JavaScript files, and tells you what's wrong. You can even run standard --fix to automatically correct most problems. The style guide it enforces includes sensible defaults: 2-space indentation, single quotes for strings, no semicolons, no unused variables, and a few other rules designed to catch real bugs (like accidentally using == instead of ===). Who uses this? Thousands of projects and companies, from major organizations like npm, GitHub, MongoDB, and Electron to countless open-source packages. The idea is that once you adopt a standard style, contributors don't waste time arguing about formatting, code reviews move faster, and the codebase stays consistent without any effort. The tool integrates with most popular code editors (VS Code, Sublime, Atom, Vim, WebStorm, etc.) so you can see style errors as you type. It's built on top of ESLint, a well-established JavaScript linter, so if you ever do need to customize rules, you can layer your own configuration on top. But the whole point of this project is that you usually don't want to, you just want something that works out of the box.