Skip to main content
Intermediate Technical IVT

linter

Pronunciation: LIN-ter

A static analysis tool that automatically examines source code to flag stylistic errors, potential bugs, and deviations from coding standards before the code is executed.

Full Definition

A linter parses source code without executing it, detecting issues such as unused variables, inconsistent indentation, deprecated function calls, and violations of a project's style guide. Popular linters include ESLint (JavaScript), Pylint (Python), and RuboCop (Ruby). In documentation, 'linter' is lowercase and the action it performs is 'linting'. Editors should note that linting is distinct from compilation and runtime testing; a linter catches code quality issues at the source level. 'Lint' as a verb ('to lint the codebase') is standard in developer content.

Usage

Usage note: Lowercase. 'Lint' as a verb is accepted in technical documentation. Distinguish from a formatter (which automatically fixes style issues) and a compiler (which transforms code).

In Context

  • "Run the linter before committing code to catch any style violations early." — Contribution guidelines
  • "The team adopted ESLint as their linter and configured it with the Airbnb style guide rules." — Engineering onboarding document

Also known as

static analyser code quality tool

Don't confuse with

compiler formatter test runner

Editors from these organisations have used our services since 1998

Reuters BBC Oxford University Press Penguin Random House Springer Microsoft Suncor Energy United Nations Fisher Investments IBM The Home Depot KODAK CHEVRON