eslint

Lint JavaScript files

$ eslint [file.js]

$ eslint [src/]

$ eslint --fix [file.js]

$ eslint -c [.eslintrc.json] [file.js]

$ eslint -f [json] [file.js]

$ eslint --init

$ eslint --ext [.js,.jsx,.ts,.tsx] [src/]

eslint [options] [files|dirs]

ESLint is the standard linting tool for JavaScript and TypeScript. It statically analyzes code to find problems, enforce coding standards, and catch bugs before runtime.
Rules are highly configurable through .eslintrc files. Plugins extend functionality for React, Vue, TypeScript, and other frameworks. The --fix flag automatically corrects many issues.
ESLint integrates with editors and CI systems, making it central to JavaScript development workflows.

FILES

Files or directories to lint.

Automatically fix problems.

Configuration file.

Output format.

File extensions to check.

Create configuration file.

Cache results for faster runs.

Report errors only.

Display help information.

.eslintrc.js / .eslintrc.json / .eslintrc.yml

Main configuration files defining rules, parser options, plugins, and extends. Can be placed in project root or any parent directory.

ESLint configuration can be embedded in the "eslintConfig" field.

Specifies files and directories to exclude from linting.

Configuration can be complex. Plugin compatibility varies. Flat config vs legacy config transition. Large codebases may be slow without caching.

ESLint was created by Nicholas C. Zakas in 2013 as a more pluggable and configurable alternative to JSHint. It became the dominant JavaScript linter due to its extensibility.

prettier(1), tsc(1), jshint(1)