JSHint
7.4#2 in lintersFree planFree planWebAPIExtensionLinux
VisitJSHint vs Luacheck
What both publish
| Fact | JSHint | Luacheck |
|---|---|---|
| Configuration | Projects can configure JSHint with a .jshintrc file, package.json jshintConfig or the CLI --config option. | Checks can be configured through command-line options, configuration files, or comments in checked files. |
| Editor integrations | The project lists integrations for Vim, Emacs, Sublime Text, Atom, TextMate, Visual Studio, VS Code, Brackets, Eclipse, NetBeans, JetBrains, Notepad++ and Gedit. | The project lists integrations for Vim, Sublime Text, Atom, Emacs, Brackets, Visual Studio Code, Nova, and Geany. |
| Installation | Official installation supports browser-like standalone files, Mozilla Rhino, npm global installation and npm development dependencies. | The project documents installation through LuaRocks and provides a single-file 64-bit Windows binary. |
| License | JSHint is licensed under the MIT Expat license. | The project is distributed under the MIT License. |
| Purpose | JSHint is a community-driven static analysis tool that detects errors and potential problems in JavaScript code. | Luacheck is a static analyzer and linter for Lua code. |
| Support | The project directs users to report bugs and suggestions through GitHub Issues. | The project directs users to its GitHub issue tracker for bugs, suggestions, and questions, and says pull requests are welcome. |
JSHint plans
- JSHintFree
Luacheck plans
- LuacheckFree
Pick JSHint if…
JSHint suits JavaScript developers who want automated checks for syntax issues and common language pitfalls. It can fit into workflows using Node.js, supported editors, or listed build integrations.
Pick Luacheck if…
It suits Lua developers who want configurable static checks locally, in editors, containers, or CI. It supports Linux, macOS, Windows, and self-hosted setups.