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 node-storage-shim.
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.
Commits
The new version differs by 9 commits.
969629dfix ci build on 6.14.4 (npx didn't exist then)
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 node-storage-shim 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 node-storage-shim.
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.
Commits
The new version differs by 9 commits.
969629dfix ci build on 6.14.4 (npx didn't exist then)1d6d25cmajor version to 2.0.0, update readme4f19866fix set trap to return true so that the module correctly runs in strict mode74ed724add typescript declaration and test33810bcupdate ci built to use 8.11.4 (lts) and 10.10.0 (current)41adb3ause proxy to intercept and correctly manage direct property accessef83ac6add failing tests showing gap in behavior when setting properties directly6b28431update deps, use chai for better assert messages, add package-lock.json4991e6cAdded test for property access, updated readme.md on limitationsSee 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: