Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update json5 to the latest version 馃殌 #533

Merged
merged 1 commit into from
Apr 12, 2018
Merged

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Mar 11, 2018

鈽濓笍 Greenkeeper鈥檚 updated Terms of Service will come into effect on April 6th, 2018.

Version 1.0.0 of json5 was just published.

Dependency json5
Current Version 0.5.1
Type dependency

The version 1.0.0 is not covered by your current version range.

If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of json5.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes 1.0.0

This release includes major internal changes and public API enhancements.

  • Major JSON5 officially supports Node.js v4 and later. Support for Node.js
    v0.10 and v0.12 have been dropped.

  • New: Unicode property names and Unicode escapes in property names are
    supported. ([#1])

  • New: stringify outputs trailing commas in objects and arrays when a space
    option is provided. ([#66])

  • New: JSON5 allows line and paragraph separator characters (U+2028 and U+2029)
    in strings in order to be compatible with JSON. However, ES5 does not allow
    these characters in strings, so JSON5 gives a warning when they are parsed and
    escapes them when they are stringified. ([#70])

  • New: stringify accepts an options object as its second argument. The
    supported options are replacer, space, and a new quote option that
    specifies the quote character used in strings. ([#71])

  • New: The CLI supports STDIN and STDOUT and adds --out-file, --space, and
    --validate options. See json5 --help for more information. ([#72], [#84],
    and [#108])

  • New: In addition to the white space characters space \t, \v, \f, \n,
    \r, and \xA0, the additional white space characters \u2028, \u2029,
    and all other characters in the Space Separator Unicode category are allowed.

  • New: In addition to the character escapes \', \", \\, \b, \f, \n,
    \r, and \t, the additional character escapes \v and \0, hexadecimal
    escapes like \x0F, and unnecessary escapes like \a are allowed in string
    values and string property names.

  • New: stringify outputs strings with single quotes by default but
    intelligently uses double quotes if there are more single quotes than double
    quotes inside the string. (i.e. stringify('Stay here.') outputs
    'Stay here.' while stringify('Let\'s go.') outputs "Let's go.")

  • New: When a character is not allowed in a string, stringify outputs a
    character escape like \t when available, a hexadecimal escape like \x0F
    when the Unicode code point is less than 256, or a Unicode character escape
    like \u01FF, in that order.

  • New: stringify checks for a toJSON5 method on objects and, if it exists,
    stringifies its return value instead of the object. toJSON5 overrides
    toJSON if they both exist.

  • New: To require or import JSON5 files, use require('json5/lib/register')
    or import 'json5/lib/register'. Previous versions used json5/lib/require,
    which still exists for backward compatibility but is deprecated and will give
    a warning.

  • New: To use JSON5 in browsers, use the file at dist/index.js or
    https://unpkg.com/json5@^1.0.0.

  • Fix: stringify properly outputs Infinity and NaN. ([#67])

  • Fix: isWord no longer becomes a property of JSON5 after calling
    stringify. ([#68] and [#89])

  • Fix: stringify no longer throws when an object does not have a prototype.
    ([#154])

  • Fix: stringify properly handles the key argument of toJSON(key) methods.
    toJSON5(key) follows this pattern.

  • Fix: stringify accepts Number and String objects as its space
    argument.

  • Fix: In addition to a function, stringify also accepts an array of keys to
    include in the output as its replacer argument. Numbers, Number objects,
    and String objects will be converted to a string if they are given as array
    values.

Commits

The new version differs by 82 commits.

There are 82 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 馃尨

@DangerCI
Copy link

DangerCI commented Mar 11, 2018

Warnings
鈿狅笍

Please add a changelog entry for your changes. You can find it in CHANGELOG.md

Please add your change and name to the master section.

鈿狅笍

Changes were made to package.json, but not to yarn.lock.
Perhaps you need to run yarn install?

Generated by 馃毇 dangerJS

greenkeeper bot added a commit that referenced this pull request Mar 18, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 18, 2018

Version 1.0.1 just got published.

Update to this version instead 馃殌

Commits

The new version differs by 6 commits.

  • 072eb40 1.0.1
  • e7bdcd1 Update CHANGELOG for v1.0.1
  • 342d575 Remove package.json5 file
  • 0336c9c Fix unclosed object and array bug
  • 25929ab Fix typo in API documentation
  • 607c18f Readme: fix typo in attribution. [skip ci]

See the full diff

@orta orta merged commit 734b4fd into master Apr 12, 2018
@orta orta deleted the greenkeeper/json5-1.0.0 branch April 12, 2018 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants