Releases: prantlf/jsonlint
Releases · prantlf/jsonlint
16.0.0
15.0.0
15.0.0 (2024-08-09)
Features
- Optionally omit object key proto and others from parsed output (e2f8a7b)
BREAKING CHANGES
Object key __proto__
and other keys from Object.prototype
are included in the parsed object by default. Earlier, no keys from Object.prototype
were included. The new behaviour is consistent with JSON.parse
. If you need the old behaviour, add the argument ignore-prototype-keys
to the command line, or set the option ignorePrototypeKeys
to true
, when calling the parse
method. If you don't have under control, what will happen with the parsed object, you should consider setting ignoreProtoKey
to true
, when calling the parse
method, to prevent prototype pollution by omitting the __proto__
key.
14.1.0
14.1.0 (2024-08-09)
Features
- Assume --trailing-commas if --trim-trailing-commas is requested (b3fb10d)
- Add options to sort object keys by locale, numerically and ignoring the letter case (4387c4b)
- Exit the process with 0 (success) if no files were found and
--succeed-with-no-files
was requested (923f37f)
Bug Fixes
- Upgrade dependencies (355aad5)
v14.0.3
v14.0.2
v14.0.1
v14.0.0
14.0.0 (2023-03-05)
Bug Fixes
- Replace commander with hand-written command-line parser (af0ea29)
BREAKING CHANGES
- Although you shouldn't notice any change on the behaviour of the command line, something unexpected might've changed. Something did change: if you're annoyed by inserting "--" between the multi-value option and other arguments, you don't have to do it any more. Multi-value options can be entered either using the option prefix multiple times for each value, or using the option prefix just once and separating the values by commas.
v13.1.0
v13.0.1
13.0.0
13.0.0 (2023-03-05)
Features
- Support JSON Schema drafts 2019-09 and 2020-12 and JSON Type Definition (0b9130c)
BREAKING CHANGES
- The default environment recognises only JSON Schema drafts 06 and 07 automatically. Not 04 any more. The environment for JSON Schema drafts 04 has to be selected explicitly. Also, JSON Schema drafts 06 and 07 are handled by AJV@8 instead of AJV@6. It shouldn't make any difference, but the implementation is new and could perform a stricter validation.