- Total 35K
- Win 16K
- Mac 13K
- Linux 6K
|Mar 26||Mar 25||Mar 24||Mar 23||Mar 22||Mar 21||Mar 20||Mar 19||Mar 18||Mar 17||Mar 16||Mar 15||Mar 14||Mar 13||Mar 12||Mar 11||Mar 10||Mar 9||Mar 8||Mar 7||Mar 6||Mar 5||Mar 4||Mar 3||Mar 2||Mar 1||Feb 28||Feb 27||Feb 26||Feb 25||Feb 24||Feb 23||Feb 22||Feb 21||Feb 20||Feb 19||Feb 18||Feb 17||Feb 16||Feb 15||Feb 14||Feb 13||Feb 12||Feb 11||Feb 10|
SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before using this plugin, you must ensure that the
jslint npm package is installed on your system.
jslint, do the following:
jslintnpm package by typing the following in a terminal:
npm install -g jslint
You may also specify the exact version of the package to be installed like this:
npm install -g firstname.lastname@example.org
If you are using
zsh, ensure that the line to load
If you are using
oh-my-zsh, do not load the
In order for
jslint 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.
Once you have installed and configured
jslint, you can proceed to install the SublimeLinter-contrib-jslint 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
jslint. Among the entries you should see
SublimeLinter-contrib-jslint. If that entry is not highlighted, use the keyboard or mouse to select it.
For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.
Linter Settings can be of use when you want to control the default behaviour of
jslint globally for all files. The
args linter setting can be used to specify options that will be passed to
jslint on every run. For example, if you want to increase the maximum number of errors
jslint will process from the default 50 to 100, you can add
"args": "--maxerr=100" to the
jslint section in SublimeLinter User settings. To list all supported options, run
jslint without options from a command prompt. You may want to refer to the readme for the
jslint npm package, and to the description of JSLint options.
Please note that options can also be specified
- in a file called
.jslintrcwritten in JSON format, specifying options as key-value pairs (refer to description of JSLint options for specifics on valid keys and values)
- globally, by placing the file in the user's home directory
- for directories or hierarchies of directories (please refer to SublimeLinter's documentation for the config_file attribute to understand where SublimeLinter will search for
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.
- Please use descriptive variable names, no abbrevations unless they are very well known.
Thank you for helping out!