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 928
  • Linux 531
Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 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
Windows 1 0 0 0 0 0 0 0 0 0 0 0 0 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
Mac 0 0 0 0 0 0 0 0 0 0 0 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 1 0 0 0 0 0 0 0 0
Linux 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 1 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).