This release includes a minor fix for indentations when stringifying empty arrays.
This release includes major internal changes and public API enhancements.
Major: JSON5 officially supports Node.js v4 LTS and v5. Support for Node.js v0.6 and v0.8 have been dropped, while support for v0.10 and v0.12 remain.
Fix: YUI Compressor no longer fails when compressing json5.js. (#97)
New: parse and the CLI provide line and column numbers when displaying error messages. (#101; awesome work by @amb26.)
Note that v0.3.0 was tagged, but never published to npm, so this v0.4.0 changelog entry includes v0.3.0 features.
This is a massive release that adds stringify support, among other things.
Major: JSON5.stringify() now exists! This method is analogous to the native JSON.stringify(); it just avoids quoting keys where possible. See the usage documentation for more. (#32; huge thanks and props @aeisenberg!)
New: NaN and -NaN are now allowed number literals. (#30; thanks @rowanhill.)
New: Duplicate object keys are now allowed; the last value is used. This is the same behavior as JSON. (#57; thanks @jordanbtucker.)
Fix: Properly handle various whitespace and newline cases now. E.g. JSON5 now properly supports escaped CR and CRLF newlines in strings, and JSON5 now accepts the same whitespace as JSON (stricter than ES5). (#58, #60, and #63; thanks @jordanbtucker.)
New: Negative hexadecimal numbers (e.g. -0xC8) are allowed again. (They were disallowed in v0.2.0; see below.) It turns out they are valid in ES5, so JSON5 supports them now too. (#36; thanks @jordanbtucker!)
This release fixes some bugs and adds some more utility features to help you express data more easily:
Breaking: Negative hexadecimal numbers (e.g. -0xC8) are rejected now. While V8 (e.g. Chrome and Node) supported them, it turns out they're invalid in ES5. This has been fixed in V8 (and by extension, Chrome and Node), so JSON5 officially rejects them now, too. (#36)
New: Trailing decimal points in decimal numbers are allowed again. (They were disallowed in v0.1.0; see below.) They're allowed by ES5, and differentiating between integers and floats may make sense on some platforms. (#16; thanks @Midar.)
New: Infinity and -Infinity are now allowed number literals. (#30; thanks @pepkin88.)
New: Plus signs (+) in front of numbers are now allowed, since it can be helpful in some contexts to explicitly mark numbers as positive. (E.g. when a property represents changes or deltas.)
Fix: unescaped newlines in strings are rejected now. (#24; thanks @Midar.)
This release tightens JSON5 support and adds helpful utility features:
New: Support hexadecimal numbers. (Thanks @MaxNanasy.)
Fix: Reject octal numbers properly now. Previously, they were accepted but improperly parsed as base-10 numbers. (Thanks @MaxNanasy.)
Breaking: Reject “noctal” numbers now (base-10 numbers that begin with a leading zero). These are disallowed by both JSON5 and JSON, as well as by ES5's strict mode. (Thanks @MaxNanasy.)
New: Support leading decimal points in decimal numbers. (Thanks @MaxNanasy.)
Breaking: Reject trailing decimal points in decimal numbers now. These are disallowed by both JSON5 and JSON. (Thanks @MaxNanasy.)
Breaking: Reject omitted elements in arrays now. These are disallowed by both JSON5 and JSON.
Fix: Throw proper SyntaxError instances on errors now.
New: Add Node.js require() hook. Register via json5/lib/require.
New: Add Node.js json5 executable to compile JSON5 files to JSON.
This was the first implementation of this JSON5 parser.
Support unquoted object keys, including reserved words. Unicode characters and escape sequences sequences aren't yet supported.
Support single-quoted strings.
Support multi-line strings.
Support trailing commas in arrays and objects.
Support comments, both inline and block.
Let‘s consider this to be Douglas Crockford’s original json_parse.js — a parser for the regular JSON format.