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

Sort Java​Script Imports

by insin ALL

Sublime Text package for sorting selected JavaScript import/require() lines by module name

Details

Installs

  • Total 3K
  • Win 2K
  • Mac 944
  • Linux 538
Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18
Windows 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sort JavaScript Imports

Adds a Sort JavaScript Imports command to Sublime Text 2 or 3, which sorts selected lines containing JavaScript import statements or require() calls by the module path they're importing.

Install via Package Control

Ctrl-Shift-P/Command-Shift-P → Package Control: Install Package → Sort JavaScript Imports

Install via git clone

Preferences → Browse Packages… → git clone https://github.com/insin/sublime-sort-javascript-imports.git "Sort JavaScript Imports"

Usage

Select lines containing the import statements you want to sort, then use either of:

  • Command palette: Ctrl-Shift-P/Command-Shift-P → Sort JavaScript Imports
  • Default key binding: Alt-F9 on Linux/Windows or Alt-F5 on Mac

Lines will be sorted based on the module path being imported, respecting (and normalising) any blank lines used to divide imports into different categories.

Any non-import lines in the selection will be moved to the end, separated by a new blank line if necessary. Let me know if there's a preferable way to handle these.

Import ordering

Where top-level imports and path-based imports are mixed in the same block, they will be ordered as follows:

  1. Top-level imports
  2. Imports which traverse up out of the current directory, from furthest away to closest
  3. Imports within the current directory

Note: if you're using Webpack aliases or a Babel alises plugin for top-level importing of your app's own code, you might want to put those in a separate block for clarity.

Example

MIT Licensed

Unit testing and configuration setup cribbed from Sort Lines (Numerically).