Bump vuex-persistedstate from 3.2.1 to 4.0.0

[dependabot-preview]

Bumps vuex-persistedstate from 3.2.1 to 4.0.0.

Release notes

Sourced from vuex-persistedstate's releases.

v4.0.0

Patches

• Remove env flag for jest: #407
• Bump shvl to fix prototype pollution issue: 20650f9c3b7f27839f78a05bd6f6cfd74e168fc5
• Update README.md: #390
• Small changes to README: b5ed167e7fc4330a91f64c056e4edc8136aaee7a

Credits

Huge thanks to @​ambianBeing and @​NeuronButter for helping!

v4.0.0-beta.3

Patches

• Bump shvl to fix prototype pollution issue. Closes #387: acefa73dbb9297a7bca665452f1df084c11101ac

v4.0.0-beta.2

Minor Changes

• Require at least RC version of Vuex: ebd71713ea41c89f7a9e81b3e6728f07162d41a3
• Remove Vue as peer dependency: a72bf84cd17ca2eb57e8e972be2f5bf33926f3f7
• Fix incorrect version of Vuex as peer: 4338d55735852cc66535969a67c3b751bb3bc2e9

Patches

• Bump shvl from 2.0.0 to 2.0.1: #295

v4.0.0-beta.1

Support For Vuex 4.0 🎉

To use the plugin with Vuex 4.0, you can initialize the plugin like the following;

import { createStore } from "vuex";
import createPersistedState from "vuex-persistedstate";
const store = createStore({
// ...
plugins: [createPersistedState()],
});

Major Changes

• Drop support for Vuex 2.0: 9c8c9d08dc85d73cf0d50e07efb360229f466fcb

Minor Changes

• Moved storage.getItem function: #299

... (truncated)

Commits

• e0bc339 v4.0.0 🎉
• 0a8300f Merge branch 'master' into 4.x.x
• 0896c39 v4.0.0-beta.3 🎉
• 4ff399b Merge branch 'master' into 4.x.x
• 580b471 v3.1.1 🎉
• 1cebcac v4.0.0-beta.2 🎉
• 4338d55 Fix incorrect version of Vuex as peer
• a72bf84 Remove Vue as peer dependency
• ebd7171 Require at least RC version of Vuex
• ff44e21 v4.0.0-beta.1 🎉
• Additional commits viewable 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 close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.