The version 2.0.0 is not covered by your current version range.
If you don’t 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’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv2.0.0
Major: JSON5 officially supports Node.js v6 and later. Support for Node.js
v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been
rewritten in native ES5, and the dependence on Babel has been eliminated.
New: Support for Unicode 10 has been added.
New: The test framework has been migrated from Mocha to Tap.
New: The browser build at dist/index.js is no longer minified by default. A
minified version is available at dist/index.min.js. ([#181])
Fix: The warning has been made clearer when line and paragraph separators are
used in strings.
Fix: package.json5 has been restored, and it is automatically generated and
committed when the version is bumped. A new build-package NPM script has
been added to facilitate this.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.0.0 of json5 was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t 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’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0Major: JSON5 officially supports Node.js v6 and later. Support for Node.js
v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been
rewritten in native ES5, and the dependence on Babel has been eliminated.
New: Support for Unicode 10 has been added.
New: The test framework has been migrated from Mocha to Tap.
New: The browser build at
dist/index.js
is no longer minified by default. Aminified version is available at
dist/index.min.js
. ([#181])Fix: The warning has been made clearer when line and paragraph separators are
used in strings.
Fix:
package.json5
has been restored, and it is automatically generated andcommitted when the version is bumped. A new
build-package
NPM script hasbeen added to facilitate this.
Commits
The new version differs by 20 commits.
3b44f2e
2.0.0
7514e54
Update dependencies
bc93dc2
Use rollup-plugin-terser
0519272
Format CHANGELOG to follow convention
02cf24c
Build non-minified browser bundle by default
6196ab0
Merge branch 'master' into v2
2c0723e
Test Node.js v10 with Travis CI
5fe80dd
Update dependencies and patch vulnerabilities
c89eeb9
Merge pull request #179 from einSelbst/master
75130f7
fix typo in Readme (Contibuting)
25acee5
Update CHANGELOG for v2.0.0
8cd89c1
Use Tap instead of Istanbul and Mocha
799098f
Update to Unicode 10
36c79eb
Set minimum Node.js version to 6.0.0
7628711
Make line and paragraph separator warning clearer
There are 20 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: