透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Closure Linter 已淘汰
隨著 JavaScript 語法持續演進 (ES2015 以上版本),要讓 Closure Linter 保持在最新狀態變得越來越困難。這個論壇沒有工作人員,也不會維護,而且已遭淘汰。
Google 的大多數專案都已遷移至新版 Lint。
如果團隊使用 Closure 工具,建議改用以 Closure 編譯器為基礎的新版 Linter。方法是將 --jscomp_warning=lintChecks
傳遞至編譯器,或建構獨立的 Linter 二進位檔;詳情請參閱
Closure 編譯器 Wiki
。對於仍在使用 Closure Linter 的團隊,本頁的其餘資訊將保留一段時間。
什麼是 Closure Linter?
Closure Linter 是一種公用程式,可檢查 JavaScript 檔案是否有樣式問題,例如運算子位置、缺少半形分號、間距、JsDoc 註解等。
Closure Linter 可以為我做什麼?
Closure Linter 可確保專案的所有 JavaScript 程式碼都符合 Google JavaScript 樣式指南的規範。還能自動修正許多常見錯誤,節省您的時間,讓您專注於編碼。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-26 (世界標準時間)。
[null,null,["上次更新時間:2025-07-26 (世界標準時間)。"],[[["\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"]]