ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-jsl

by SublimeLinter ST3

SublimeLinter plugin for JavaScript, using JavaScript Linter (jsl).

Details

Installs

  • Total 27K
  • Win 15K
  • OS X 7K
  • Linux 5K
Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5
Windows 16 23 11 7 21 12 7 15 19 9 22 10 12 5 11 7 14 14 15 13 18 7 13 15 12 19 11 8 16 12 14 18 14 15 11 16 28 19 10 14 12 13 10 17 15 6
OS X 9 5 6 5 9 5 5 8 3 5 11 9 2 3 4 5 3 11 7 5 6 3 2 9 7 6 6 1 5 7 6 6 4 2 6 6 15 7 9 3 0 1 7 6 2 4
Linux 1 2 2 3 3 5 2 6 4 5 5 4 4 5 4 2 2 1 5 1 2 1 4 3 2 5 5 0 5 5 2 2 9 3 4 2 2 7 2 1 2 1 2 5 2 3

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-jsl

Build Status Codacy Badge

This linter plugin for SublimeLinter provides an interface to jsl (JavaScript Lint). It will be used with files that have the “JavaScript” syntax, or within <script> tags in HTML files.

Installation

SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.

Linter installation

Before installing this plugin, you must ensure that jsl 0.3.0 is installed on your system. To install jsl, download and install the appropriate package from the JavaScript Lint download page.

NOTE: Do not use the latest development version from svn. This plugin is only compatible with one of the 0.3.0 releases.

Linter configuration

In order for jsl 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 jsl is installed and configured, you can proceed to install the SublimeLinter-jsl plugin if it is not yet installed.

Plugin installation

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:

  1. 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.

  2. When the plugin list appears, type jsl. Among the entries you should see SublimeLinter-jsl. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

You can configure jsl options in the way you would from the command line, with jsl.conf files. For more information, see the jsl docs. The linter plugin does this by searching for a jsl.conf file itself in the linted file's working directory, its parent directories, and the user's home directory (~).

You may provide a custom config file by setting the linter's "args" setting to ["-conf", "/path/to/file"]. To create a jsl config file, type the following in a terminal:

jsl -help:conf > jsl.conf

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic branch.
  4. Make a pull request.
  5. 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.
IMPORTANT!

Also note that this repository uses overcommit as a validation tool. Before making any changes, please install overcommit in your local repository.

Thank you for helping out!