- Total 292K
- Win 140K
- OS X 103K
- Linux 49K
|Dec 14||Dec 13||Dec 12||Dec 11||Dec 10||Dec 9||Dec 8||Dec 7||Dec 6||Dec 5||Dec 4||Dec 3||Dec 2||Dec 1||Nov 30||Nov 29||Nov 28||Nov 27||Nov 26||Nov 25||Nov 24||Nov 23||Nov 22||Nov 21||Nov 20||Nov 19||Nov 18||Nov 17||Nov 16||Nov 15||Nov 14||Nov 13||Nov 12||Nov 11||Nov 10||Nov 9||Nov 8||Nov 7||Nov 6||Nov 5||Nov 4||Nov 3||Nov 2||Nov 1||Oct 31||Oct 30|
SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before installing this plugin, you must ensure that
jshint is installed on your system. To install
jshint, do the following:
npm install -g jshint
- If you are using
zsh, ensure that the line to load
.zshrc.(reason: here and here)
Note: This plugin requires
jshint 2.5.0 or later. Please note that the indent option no longer reports warnings for bad indentation. https://github.com/jshint/jshint/releases/tag/2.5.0
In order for
jshint to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.
jshint is installed and configured, you can proceed to install the SublimeLinter-jshint plugin if it is not yet installed.
Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.
To install via Package Control, do the following:
Within Sublime Text, bring up the Command Palette and type
install. Among the commands you should see
Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.
When the plugin list appears, type
jshint. Among the entries you should see
SublimeLinter-jshint. If that entry is not highlighted, use the keyboard or mouse to select it.
You can configure
jshint options in the way you would from the command line, with
.jshintrc files. For more information, see the jshint docs. The linter plugin does this by searching for a
.jshintrc file itself, just as
jshint does from the command line. You may provide a custom config file by setting the linter’s
"args" setting to
["--config", "/path/to/file"]. On Windows, be sure to double the backslashes in the path, for example
The path to the
.jshintrc file is cached, meaning if you create a new
.jshintrc that should have precedence over the previous one (meaning it is closer to the .js file) you need to clear the cache for the linter to use the new
.jshintrc You can clear the cache by going to: Tools > SublimeLinter > Clear Caches.
Using with tabs
If you use tabs as your indentation, make sure you set the option
indent: 1 in your .jshintrc file. If not the wrong sections of the code will be highlighted.
If you would like to contribute enhancements or fixes, please do the following:
- Fork the plugin repository.
- Hack on a separate topic branch created from the latest
- Commit and push the topic branch.
- Make a pull request.
- Be patient. ;-)
Please note that modications should follow these coding guidelines:
- Indent is 4 spaces.
- Code should pass flake8 and pep257 linters.
- Vertical whitespace helps readability, don’t be afraid to use it.
Thank you for helping out!