Stay organized with collections
Save and categorize content based on your preferences.
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
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. It can also automatically fix many
common errors, which saves you time and lets you focus on coding.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2023-10-25 UTC.
[null,null,["Last updated 2023-10-25 UTC."],[[["\u003cp\u003eClosure Linter is deprecated and no longer actively maintained due to difficulties in keeping up with evolving JavaScript syntax.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using the new linter integrated with Closure Compiler by passing \u003ccode\u003e--jscomp_warning=lintChecks\u003c/code\u003e to the compiler or building the standalone linter binary.\u003c/p\u003e\n"],["\u003cp\u003eClosure Linter, while deprecated, is a tool used for checking JavaScript files for style issues, ensuring code follows Google JavaScript Style Guide, and automatically fixing common errors.\u003c/p\u003e\n"]]],[],null,["Closure Linter is deprecated\n----------------------------\n\n\nAs the syntax of JavaScript has continued to evolve, with ES2015\nand beyond, it has become increasingly difficult to keep Closure\nLinter up to date. It is unstaffed, unmaintained, and deprecated.\nMost projects at Google have migrated to the new linter.\n\n\nFor teams using the Closure tools, we recommend they use the new\nlinter based on the Closure Compiler instead. You can do this by\npassing `--jscomp_warning=lintChecks` to the compiler,\nor building the standalone linter binary; see the\n[Closure Compiler wiki](https://github.com/google/closure-compiler/wiki/Lint-checks) for details. The rest of the information on this page will be\nkept up for a while, for teams who are still using Closure Linter.\n\nWhat is the Closure Linter?\n---------------------------\n\n\nThe Closure Linter is a utility that checks JavaScript files for\nstyle issues such as operator placement, missing semicolons,\nspacing, the presence of JsDoc annotations, and more.\n\nWhat can the Closure Linter do for me?\n--------------------------------------\n\n\nThe Closure Linter ensures that all of your project's JavaScript\ncode follows the guidelines in\nthe [Google\nJavaScript Style Guide](https://google.github.io/styleguide/javascriptguide.xml). It can also automatically fix many\ncommon errors, which saves you time and lets you focus on coding. \n\nHow do I start?\n---------------\n\n\n- [Download Closure Linter](https://github.com/google/closure-linter/zipball/master).\n- Read [How to Use Closure Linter](/closure/utilities/docs/linter_howto).\n- Browse [the source code](https://github.com/google/closure-linter/).\n- Questions? Ask the [discussion forum](http://groups.google.com/group/closure-linter-discuss).\n\n\u003cbr /\u003e"]]