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

Sublime​Linter-contrib-eslint_d

by roadhump ST3

This linter plugin for SublimeLinter provides an interface to eslint_d

Details

Installs

  • Total 18K
  • Win 7K
  • OS X 9K
  • Linux 3K
May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8
Windows 14 33 22 18 13 26 29 34 33 36 18 20 21 27 32 38 18 14 26 32 30 33 16 30 30 29 40 50 39 41 29 15 15 50 27 45 40 50 13 24 27 33 48 46 45 25
OS X 7 24 33 9 17 25 40 26 41 35 9 10 17 29 23 29 18 12 20 33 30 39 23 23 16 26 30 26 36 35 31 9 13 33 44 37 31 40 10 19 35 35 31 29 27 13
Linux 1 8 10 5 3 7 5 8 13 8 4 6 8 9 6 6 8 5 3 11 8 10 9 7 6 5 5 7 6 6 4 4 4 4 6 8 14 5 4 5 6 8 9 9 9 5

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-eslint_d

Build Status

This linter plugin for SublimeLinter provides an interface to eslint_d. It will be used with files that have the “JavaScript” syntax.

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 using this plugin, you must ensure that eslint_d is installed on your system. To install eslint_d, do the following:

  1. Install Node.js (and npm on Linux).

  2. Install eslint_d by typing the following in a terminal:

npm install -g eslint_d

Or install eslint_d locally in your project folder (you must have package.json file there):

```
   npm init -f
   npm install eslint_d
   ```
  1. If you are using nvm and zsh, ensure that the line to load nvm is in .zshenv and not .zshrc.

  2. If you are using zsh and oh-my-zsh, do not load the nvm plugin for oh-my-zsh.

Note: This plugin requires eslint_d 2.3.1 or later.

Linter configuration

In order for eslint_d 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 eslint_d, you can proceed to install the SublimeLinter-contrib-eslint_d 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 eslint_d. Among the entries you should see SublimeLinter-contrib-eslint_d. 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 eslint options in the way you would from the command line, with .eslintrc files. For more information, see the eslint docs.

FAQ and Troubleshooting

This plugin is almost similar to SublimeLinter-contrib-eslint, so you can use its documentation, just replace eslint with eslint_d.

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 modifications 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 abbreviations unless they are very well known.

Thank you for helping out!