Update electron-json-storage: 4.1.5 → 4.5.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ electron-json-storage (4.1.5 → 4.5.0) · Repo · Changelog

Release Notes

4.5.0 (from changelog)

• Add a .getSync() function

4.4.0 (from changelog)

• Gracefully require the user to call .setDataPath() if the remote module is not available when running on a renderer process

4.3.0 (from changelog)

• Add a prettyPrinting option to .set()

4.2.0 (from changelog)

• Support a validate boolean option in .set() to validate writes by reading the key back after a short period of time and re-trying the write if the contents do not match

4.1.8 (from changelog)

• Don't list non-JSON files in .keys()

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 54 commits:

• Merge pull request #164 from electron-userland/upgrade-4-5-0
• Upgrade to v4.5.0
• Merge pull request #163 from electron-userland/get-sync
• Add a .getSync() function
• Merge pull request #161 from Slapbox/patch-1
• Adds missing word "not"
• Merge pull request #160 from electron-userland/v4.4.0
• v4.4.0
• Merge pull request #158 from electron-userland/dependabot/npm_and_yarn/electron-10.2.0
• Merge pull request #159 from electron-userland/optional-remote-module
• Graceful fallback if the renderer process can't access the remote module
• Bump electron from 10.1.3 to 10.2.0
• Merge pull request #154 from electron-userland/dependabot/npm_and_yarn/ini-1.3.7
• Bump ini from 1.3.5 to 1.3.7
• Merge pull request #153 from electron-userland/4-3-0
• v4.3.0
• Merge pull request #152 from electron-userland/pretty-printing-tests
• Add unit tests for the new prettyPrinting option
• Merge pull request #151 from Unknown025/master
• Change spacing option to prettyPrinting.
• Added spacing option for writing to JSON.
• Merge pull request #148 from electron-userland/no-remote-docs
• Show how to avoid using `electron.remote` on renderer processes
• Merge pull request #147 from electron-userland/upgrade-electron-deps
• Upgrade Electron deps
• Merge pull request #144 from electron-userland/dependabot/npm_and_yarn/lodash-4.17.19
• Bump lodash from 4.17.13 to 4.17.19
• Merge pull request #142 from electron-userland/dependabot/npm_and_yarn/lodash-4.17.13
• Merge pull request #143 from electron-userland/new-version
• v4.2.0
• Bump lodash from 4.17.11 to 4.17.13
• Merge pull request #128 from electron-userland/retry-size-zero
• Retry write if resulting file size is zero when using validate=true
• Merge pull request #141 from electron-userland/dependabot/npm_and_yarn/electron-7.2.4
• Update Node.js in Travis CI and Appveyor CI
• Upgrade electron-mocha to v9.0.1
• Bump electron from 2.0.14 to 7.2.4
• Merge pull request #138 from electron-userland/4-1-8
• v4.1.8
• Merge pull request #137 from electron-userland/only-list-json-keys
• Only list JSON files in .keys()
• Merge pull request #136 from electron-userland/update-4-1-7
• v4.1.7
• Merge pull request #135 from electron-userland/appveyor-master
• Merge pull request #133 from bikov/master
• Only build Appveyor branches on master
• Merge branch 'master' of https://github.com/bikov/electron-json-storage
• allow to read file that saved in other encodings then utf-8
• Merge pull request #134 from electron-userland/fix-travis
• Fix Travis CI
• allow to read file that saved in other encodings then utf-8
• v4.1.6
• Merge pull request #124 from electron-userland/atomic-writes
• Implement atomic writes

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #47.