Once installed, either call
sortjson with file name, folder name or a list thereof, with or without flags:
$ jsonsort file1.json "folder1/folder2/**/*.*" folder3 -s $ jsonsort * -t -n -s $ jsonsort yourspecialfolder -s $ jsonsort -v $ jsonsort --version $ jsonsort -h $ jsonsort --help
sortjson, same thing. We wired up both. See the API section (of call for help via CLI,
|Don't ignore any node_modules folders and package-lock.json's|
|Use tabs for JSON file indentation|
|How many spaces or tabs to use (default = 2 spaces or 1 tab)|
|When on, no output is shown. If enabled, you'll distinguish success from failure by exit code.|
|Also sort any arrays if they contain only string elements|
|Shows (similar to this) help|
|Shows the installed version of your |
|Skip all |
|Only output the paths of the files|
|Does nothing, exits with non-zero code if files COULD BE sorted, with zero code if no sort needed.|
Put either short or long version of a desired flag, before or after the path or list of paths. For example, all these commands below are the same:
jsonsort templates/springsale03 -s
jsonsort -s templates/springsale03
jsonsort templates/springsale03 --silent
jsonsort --silent templates/springsale03
It sorts JSON files deeply.
That is, it does not matter is it's a plain object within array within array within a plain object - all objects no matter how deep, will be detected and sorted.
If this tool processes any
package.json files (put
-p to disable this), it will first deep-sort alphabetically, then use
format-package (npm) to arrange keys according to a commonly agreed format —
name at the top, depedencies at the bottom etc.
This is a parsing-type application, so written files are also prettified — tabulations and whitespace are fixed to an (arbitrary) order. If you leave the default setting, it will indent using two spaces. If you call it with a flag
-t, one tab will be used.
package.jsonare first deep-sorted alphabetically, then using
format-package(npm) (on by default, but put
-pto disable this)
- Works on dot files, as long as they are parse-able as JSON
- Can process a set of files in folder (use wildcards for example,
- Broken JSON files don't stop the process, other healthy files from batch are still sorted. Notifies user.
- System files like
.DS_Storeare not processed by default, don't worry about excluding them in the input path.
When in CI mode, this CLI won't amend the files, only calculate the sorted result, compare the file's contents with it, then exit with a:
- zero code, if sorting would make no difference to a file
- non-zero code, if sorting would not make any difference
Basically, your scripts with this CLI would fail on unsorted JSON's. Thanks widerin for the idea for this feature.
CI mode does not write files, only exits with one code or another.