Installations

npm install @r1chm8/eslint-plugin-sort-destructure-keys

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

>=6.0.0

Node Version

16.13.2

NPM Version

8.1.2 Pull Requests

Open

8

Total

283

Closed

65

Merged

210

Issues

Open

2

Total

19

Closed

17

Releases

Unable to fetch releases

Contributors

7

Unable to fetch Contributors

View all 7 contributors

Languages

1

JavaScript

JavaScript (100%)

Developer

mthadley

Download Statistics

Total Downloads

30,785

Last Day

30

Last Week

109

Last Month

608

Last Year

8,574

GitHub Statistics

95 Stars

490 Commits

9 Forks

2 Watching

9 Branches

7 Contributors

Bundle Size

2.56 kB

Minified

1.25 kB

Minified + Gzipped

Bundlephobia

Maintainers

1

Package Meta Information

Latest Version

0.0.1

Package Id

@r1chm8/eslint-plugin-sort-destructure-keys@0.0.1

Unpacked Size

10.63 kB

Size

4.03 kB

File Count

6

NPM Version

8.1.2

Node Version

16.13.2

Total Downloads

Cumulative downloads

Total Downloads

30,785

Last day

42.9%

30

Compared to previous day

Last week

-18.7%

109

Compared to previous week

Last month

12.2%

608

Compared to previous month

Last year

-42.4%

8,574

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

natural-compare-lite

Peer Dependencies

1

eslint

Dev Dependencies

5

@babel/core @babel/eslint-parser eslint mocha prettier

Versions

eslint-plugin-sort-destructure-keys

require object destructure key to be sorted

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install eslint-plugin-sort-destructure-keys:

$ npm install eslint-plugin-sort-destructure-keys --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-sort-destructure-keys globally.

Usage

Add sort-destructure-keys to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

1{
2    "plugins": [
3        "sort-destructure-keys"
4    ]
5}

Then configure the rule under the rules section.

1{
2    "rules": {
3        "sort-destructure-keys/sort-destructure-keys": 2
4    }
5}

Rule Options

1{
2    "sort-destructure-keys/sort-destructure-keys": [2, {"caseSensitive": false}]
3}

`caseSensitive`

When true the rule will enforce properties to be in case-sensitive order. Default is true.

Example of incorrect code for the {"caseSensitive": false} option:

1let {B, a, c} = obj;

Example of correct code for the {"caseSensitive": false} option:

1let {a, B, c} = obj;

Example of incorrect code for the {"caseSensitive": true} option:

1let {a, B, c} = obj;

Example of correct code for the {"caseSensitive": true} option:

1let {B, a, c} = obj;

Changelog

`1.4.0`

Add compatibility with eslint 8. (#123)

`1.3.5`

Add ^7.0.0 to eslint peer dependency. (#53, by dsernst)

`1.3.4`

Fixes TypeError issue with multiple property expressions (#20)

`1.3.3`

Add 6.0.0 to eslint peer dependency. (#21, by @7rulnik)

`1.3.2`

Fix bug where computed properties were causing the rule to throw errors. (#15, thanks @TSMMark!)

`1.3.1`

Fix bug with rest properties being sorted incorrectly. (#11, #12, thanks @briandastous and @njdancer!)

`1.3.0`

Add support for --fix eslint cli flag

`1.2.0`

Add peer dependency support for eslint ^5.0.0

`1.1.0`

Add caseSensitive option (#1 by @bsonntag)

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

6

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

3.5

/10

Last Scanned on 2025-01-27

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More