Releases: prantlf/jsonlint
Releases · prantlf/jsonlint
v6.2.1
v6.2.0
v6.1.0
6.1.0 (2019-05-27)
Bug Fixes
- Fix the missing function object (Parser) in the main module exports (eb892aa)
- Restore context options (yy) set in the Parser constructor after the call to parse, if the options were overridden by the method arguments (787c350)
Features
- Use the native JSON parser if a limited error information is enough (8aa9fb1)
v6.0.0
6.0.0 (2019-05-26)
Features
- Declare modules in this package using UMD (d442583)
- Remove ParserWithComments and parseWithCOmment from the interface (3fab374)
BREAKING CHANGES
- The object and the method do not exist any more. Pass the parameter "ignoreComments" as an object
{ ignoreComments: true }
either to the constructor of theParser
object, or as the second parameter to the methodparse
.
v5.0.0
5.0.0 (2019-05-26)
Bug Fixes
- Do not export "main" method, which requires other NPM modules (d8af36a)
Features
- Accept single quotes (apostrophes) as string delimiters (240b8cd)
BREAKING CHANGES
- The "main" method providing a command-line interface importable from other module has been removed. If you used it, have a look at the command-line interface in
lib/cli
. You can import this module in instead and it offers a richer interface, than the previously exported "main" method. Thelib/cli
module is mapped tobin/jsonlint
too. However, consider the default library export (lib/jsonlint
) for programmatic usage. You will pack less JavaScript code and use smalker, mode programmer-oriented interface.
v4.0.2
v4.0.1
v4.0.0
4.0.0 (2019-05-19)
Bug Fixes
- Standardize the interface of the "jsonlint/lib/formatter" module (b8b041b)
Features
- Add web and programmatic interfaces to JSON Schema validation (d45b243)
BREAKING CHANGES
- The formatting method is exposed not as exports.formatter.formatJson, but as exports.format.
This module is not documented and it is unlikely, that it broke other project.
v3.0.0
3.0.0 (2019-05-18)
Bug Fixes
- Replace JSON schema validator JSV with ajv, because JSV is not maintained any more and does not support current JSON schema drafts (1a4864f)
BREAKING CHANGES
- The environment for the JSON schema validation "json-schema-draft-03" is not available any more.
Migrate your schemas from the JSON schema draft 03 to 04 or newer. Drafts 04, 06 and 07 are supported with this release.