sort-named-exports
Enforce sorted named exports.
Maintaining a consistent and sorted order of named exports can significantly improve code readability.
This rule ensures that named exports are organized in a predictable manner, making it easier for developers to navigate and manage exported modules. By adopting this practice, you enhance the maintainability and clarity of your codebase.
Try it out
Options
This rule accepts an options object with the following properties:
type
default:'alphabetical'
Specifies the sorting method.
'alphabetical'
— Sort items alphabetically (e.g., “a” < “b” < “c”).'natural'
— Sort items in a natural order (e.g., “item2” < “item10”).'line-length'
— Sort items by the length of the code line (shorter lines first).
order
default:'asc'
Determines whether the sorted items should be in ascending or descending order.
'asc'
— Sort items in ascending order (A to Z, 1 to 9).'desc'
— Sort items in descending order (Z to A, 9 to 1).
ignoreCase
default:true
Controls whether sorting should be case-sensitive or not.
true
— Ignore case when sorting alphabetically or naturally (e.g., “A” and “a” are the same).false
— Consider case when sorting (e.g., “A” comes before “a”).
specialCharacters
default:keep
Controls whether special characters should be trimmed, removed or kept before sorting.
'keep'
— Keep special characters when sorting (e.g., “_a” comes before “a”).'trim'
— Trim special characters when sorting alphabetically or naturally (e.g., “_a” and “a” are the same).'remove'
— Remove special characters when sorting (e.g., “/a/b” and “ab” are the same).
groupKind
default:'mixed'
Allows you to group named exports by their kind, determining whether value exports should come before or after type exports.
mixed
— Do not group named exports by their kind; export statements are sorted together regardless of their type.values-first
— Group all value exports before type exports.types-first
— Group all type exports before value exports.
partitionByComment
default:false
Allows you to use comments to separate the members of named exports into logical groups. This can help in organizing and maintaining large enums by creating partitions within the enum based on comments.
true
— All comments will be treated as delimiters, creating partitions.false
— Comments will not be used as delimiters.string
— A glob pattern to specify which comments should act as delimiters.string[]
— A list of glob patterns to specify which comments should act as delimiters.
partitionByNewLine
default:false
When true
, the rule will not sort the members of named exports if there is an empty line between them. This can be useful for keeping logically separated groups of members in their defined order.
export {
// Group 1
Drone,
Keyboard,
Mouse,
Smartphone,
// Group 2
Laptop,
Monitor,
Smartwatch,
Tablet,
// Group 3
Headphones,
Router,
} from './devices'
Each group of members (separated by empty lines) is treated independently, and the order within each group is preserved.
matcher
default:'minimatch'
Determines the matcher used for patterns in the partitionByComment
option.
'minimatch'
— Use the minimatch library for pattern matching.'regex'
— Use regular expressions for pattern matching.
Usage
Version
This rule was introduced in v0.4.0.