Bump gun from 0.3.9991 to 0.2019.930 in /examples

[dependabot]

Bumps gun from 0.3.9991 to 0.2019.930.

Release notes

Sourced from gun's releases.

0.2019.413

No release notes provided.

0.9.999998

No release notes provided.

0.7.0

No release notes provided.

0.6.3

Significant changes from previous tags, check the changelog and documentation for migrations.

Changelog

Sourced from gun's changelog.

CHANGELOG

0.9.x

No breaking changes, but the new Radix Storage Engine (RSE) has been finally integrated and works with S3 as a backup. Expect an order of magnitude or more in cost savings, we'll report our December bill compared to November when we get it.

We have successfully benchmarked it against 1,000,000 records doing end-to-end triple verification using our Jepsen-inspired PANIC distritubed testing framework, doing ~4K acked writes/second on a Macbook Air dev machine. For more information on PANIC, check out this 5 minute presentation we did in Sweden (and the prior talk, for those interested in porting GUN out of its reference implementation of JS).

Warning: There is a known rare edge case in RSE currently, if data is split between two chunked files, a GET will only return from the first chunk. This will be fixed soon, but we still encourage developers to run and test against it, please report any problems.

To use RSE, initialize a gun server peer with the default storage disabled, like Gun({localStorage: false}). Want to use it with S3? All you need to do is make sure that your environment variables are configured and it will automatically use S3, here is a template. This works especially well for our 1-click-deploy Heroku demo server with the example apps.

Finally, with end-to-end encryption being enabled with our Security, Encryption, Authorization (SEA) framework (check out our P2P/decentralized crypto-identity blockchain), gun is marching towards a stable v1.0 production-ready system (it is already being used in production by a Northern European government's Navy). So if you are able to work around the remaining bugs, we would appreciate everybody efforts in experimenting and testing out gun and reporting any last hiccups in our lead up to the v1.0!

We will be overhauling documentation in this v0.9.x series, please make complaints about what is missing, and how we can make it better, so it will be polished for the v1.0! The chatroom is actively and friendly for help, StackOverflow for questions. And we're looking for sponsors, we regularly get 1,200+ uniques every 2 weeks on this repo, we've had 53% monthly growth on our installs, and GUN is ranked in the top quarter of the top 1% of the top 1% fastest growing projects across all GitHub! If you are an Enterprise, this would be a great time to chat with us about our IoT, AI/ML, edge computing, graph, and cybersecurity solutions.

Here is towards a v1.0! Cheers.

0.8.x

Adapter interfaces have changed from Gun.on('event', cb) to gun.on('event', cb), this will force adapters to be instance specific.

.path() and .not() have been officially removed from the core bundle, you can bundle them yourself at lib/path.js and lib/not.js if you still need them.

0.7.x

Small breaking change to .val(cb):

Previously .val(cb) would ONLY be called when data exists, like .on(cb).

However, due to popular demand, people wanted .val(cb) to also get called for .not(cb) rather than (before) it would "wait" until data arrived.

NOTE: For dynamic paths, .val(cb) will still wait, like:

gun.get('users').map().val(cb) because the behavior of the map() is simply to not fire anything down the chain unless items are found.

0.6.x

Introduced experimental features, chaining .val() (no callback) and .map(cb) behaving as a map/reduce function.

It also upgraded the socket adapters and did end-to-end load testing and correctness testing.

0.5.9

GUN 0.3 -> 0.4 -> 0.5 Migration Guide:
gun.back -> gun.back();
gun.get(key, cb) -> cb(err, data) -> cb(at) at.err, at.put;
gun.map(cb) -> gun.map().on(cb);
gun.init -> deprecated;
gun.put(data, cb) -> cb(err, ok) -> cb(ack) ack.err, ack.ok;

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.