## Closure Linter is deprecated


As the syntax of JavaScript has continued to evolve, with ES2015
and beyond, it has become increasingly difficult to keep Closure
Linter up to date. It is unstaffed, unmaintained, and deprecated.
Most projects at Google have migrated to the new linter.


For teams using the Closure tools, we recommend they use the new
linter based on the Closure Compiler instead. You can do this by
passing `--jscomp_warning=lintChecks` to the compiler,
or building the standalone linter binary; see the
[Closure Compiler wiki](https://github.com/google/closure-compiler/wiki/Lint-checks) for details. The rest of the information on this page will be
kept up for a while, for teams who are still using Closure Linter.

## What is the Closure Linter?


The Closure Linter is a utility that checks JavaScript files for
style issues such as operator placement, missing semicolons,
spacing, the presence of JsDoc annotations, and more.

## What can the Closure Linter do for me?


The Closure Linter ensures that all of your project's JavaScript
code follows the guidelines in
the [Google
JavaScript Style Guide](https://google.github.io/styleguide/javascriptguide.xml). It can also automatically fix many
common errors, which saves you time and lets you focus on coding.

## How do I start?


- [Download Closure Linter](https://github.com/google/closure-linter/zipball/master).
- Read [How to Use Closure Linter](https://developers.google.com/closure/utilities/docs/linter_howto).
- Browse [the source code](https://github.com/google/closure-linter/).
- Questions? Ask the [discussion forum](http://groups.google.com/group/closure-linter-discuss).

<br />