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

Standard​Format

by bcomnes ST3

:sparkles: Runs standard --fix against the javascript in your ST3 window on save or manually.

Details

Installs

  • Total 20K
  • Win 9K
  • Mac 8K
  • Linux 4K
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 29 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 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4
Windows 1 1 1 0 0 1 0 0 0 0 1 0 0 0 0 1 0 1 2 0 0 2 0 0 1 0 0 1 0 3 1 0 2 0 2 1 0 0 1 0 0 2 0 2 1
Mac 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0 0 0 0 0 0 1 1 1 0 1 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 1 0 1 0 0 1 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Standard Format

tests

A Sublime Text 3 plug-in that runs standard –fix against the javascript code in your ST3 window on save or manually. Can be toggled on or off. Includes a few settings that let you tweak your search path to favor local dependencies over global ones.

Supports any tool that accepts a stdin and stdout formatting API. The following tools are used by default:

standard --fix
semistandard --fix

action gif

Installation

Install Standard Format using Package Control.

# In the command palate
- package control install
- standard format

Standard Format (the Sublime Text Plug-in) requires that you install standard either locally to your project or globally. It is recomended to save it to your local project.

$ npm install standard@latest --save-dev

Configuration

You can find Standard Format settings in the StandardFormat.sublime-settings file.

Standard Format is agressive about finding your developer dependencies. The search path that it uses by default are in the following order:

  • User added paths: you can add an array of paths in your settings file. You shouldn't need to do this unless you are doing something weird.
  • Any node_modules/.bin paths found above the current file. Disable with use_view_path
  • If your current view isn't saved to disk, any any folders in the project will be walked towards root searching for node_modules/.bin to add to the path here. Disabled with use_project_path_fallback.
  • The global user path is then used if nothing else is found. This is calculated by starting a bash instance and calculating the real user path, including .nvm shims.

Other settings:

  • format_on_save: Boolean. Runs Standard Format on save when set to true. Use the command pallet to quickly toggle this on or off.
  • extensions: String Array. An array of file extensions that you want to be able to run Standard Format against.

  • command: Optional String Array. Customize the command and flags that Standard Format runs against. Can expand certain pre-defined placeholders (such as {FILENAME}).

Default:

{
  "commands": [
    ["standard", "--stdin", "--fix"],
    ["semistandard", "--stdin", "--fix" ]
    ["ts-standard", "--stdin", "--fix", "--stdin-filename", "{FILENAME}" ]
  ]
}
  • loud_error: Boolean. Specifies if you get a status bar message or error window if the subprocess encounters an error while formatting.

  • log_errors: Boolean. Lets you log out errors encountered by the formatter. Mainly used to suppress noisy formatting errors.

Project local settings

If the default/user settings isn't fined grained enough, you can set project specific settings in .sublime-project project specific settings. See sublime project docs for more details.

{
  "settings": {
    "standard_format": {
      "format_on_save": true,
      "commands": [
        ["eslint_d", "--stdin", "--fix-to-stdout"]
      ]
    }
  }
}

Hints

Windows is now supported. Please open any issues that you come across.

Linter

Standard Format pairs nicely with the Sublime Text standard linter:

References