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

Sublime​Linter-flow

by SublimeLinter ST3

SublimeLinter plugin for JavaScript static type checking, using flow.

Details

Installs

  • Total 8K
  • Win 2K
  • OS X 5K
  • Linux 1K
Oct 24 Oct 23 Oct 22 Oct 21 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
Windows 0 4 2 2 2 9 5 8 1 2 1 2 0 3 2 2 4 3 1 3 1 6 2 2 0 1 2 4 6 3 2 2 2 1 4 7 2 4 1 4 11 5 2 2 2 1
OS X 4 6 6 6 12 11 7 9 5 4 2 14 12 7 11 8 6 5 7 16 9 15 9 4 5 6 8 13 17 7 8 4 5 10 7 9 14 9 6 12 25 19 11 7 7 4
Linux 1 4 1 0 5 3 3 3 1 1 0 3 1 2 3 1 2 2 1 1 5 2 3 1 0 1 2 5 2 2 1 1 1 0 2 4 4 1 2 1 8 4 2 1 1 0

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-flow

Build Status

This linter plugin for SublimeLinter provides an interface to flow, a static type checker for JavaScript. 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 flow is installed on your system. To install flow, follow the instructions here:

Getting started with Flow

In order for this linter to work you will need to run the flow init command in your project or manually create a .flowconfig file.

Note: This plugin requires flow 0.1.0 or later.

Linter configuration

In order for flow 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 flow, you can proceed to install the SublimeLinter-flow 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 flow. Among the entries you should see SublimeLinter-flow. 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.

In addition to the standard SublimeLinter settings, SublimeLinter-flow provides its own settings. Those marked as “Inline Setting” may also be used inline.

Setting Description Inline Setting
lib Add a path to your interface files. More info
show-all-errors It allows flow to output all errors instead of stopping at 50
flow-bin Allows to specify the path to the flow executable
coverage Shows flow coverage warnings
all runs flow against all files regardless of @flow comment

Warning

At this moment, using all in a medium to big sized node.js project may cause a crash. It's recommended to use flow incrementally, one file at a time.

Use with caution.

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!