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

Sublime​Linter-contrib-semistandard

by Flet ST3

No description provided

Details

Installs

  • Total 2K
  • Win 498
  • OS X 860
  • Linux 262
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 Sep 4
Windows 0 0 0 0 0 0 0 1 1 2 0 1 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 2 2 3 2 1 0 2 3 1 0 0 2 0 0 0 6 1
OS X 0 0 2 0 0 1 0 1 0 1 0 0 4 0 1 0 2 1 0 0 1 2 2 1 0 0 1 3 4 1 2 0 0 1 0 7 0 0 1 1 0 2 1 0 2
Linux 0 0 0 0 0 0 0 0 2 0 0 3 0 0 0 1 0 0 1 0 0 1 0 2 0 0 1 0 0 0 1 1 0 1 0 0 1 1 0 1 0 0 4 0 0

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-semistandard

Build Status

This linter plugin for SublimeLinter provides an interface to semistandard. 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 semistandard is installed on your system. To install semistandard, do the following:

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

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

npm install -g semistandard
  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 semistandard 2.3.2 or later.

Linter configuration

In order for semistandard 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 semistandard, you can proceed to install the SublimeLinter-contrib-semistandard 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 semistandard. Among the entries you should see SublimeLinter-contrib-semistandard. If that entry is not highlighted, use the keyboard or mouse to select it.

Automatic Formatting

This can be accomplished via @bcomnes StandardFormat on package control.

1) Make sure you have at least semistandard-format, just update to the latest to be sure:

npm install semistandard-format -g

2) Install StandardFormat from package control 3) Open the “user” package settings for “Standard Format” - via command pallete: standard format settings user - or via menu: Preference > Package Settings > Standard Format > Settings - User

4) Add a reference to semistandard-format --stdin:

{
  // set this to false if you don't want to format on save
  "format_on_save": true,
  "command": ["semistandard-format", "--stdin"],
}

5) Save the settings file. 6) Restart Sublime Text.

StandardFormat will also map CTRL+ALT+F to format automatically. :)

Settings

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

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!