Bump vuex from 3.5.1 to 4.1.0 in /frontend

[dependabot]

Bumps vuex from 3.5.1 to 4.1.0.

Release notes

Sourced from vuex's releases.

v4.0.2

Bug Fixes

• devtools: fix no getters displayed on root module + better getters inspector (#1986) (bc20295)
• build: cjs build failing due to __VUE_PROD_DEVTOOLS__ defined (#1991) (#1992) (7151622)

v4.0.1

Features

• dx: add devtools integration (#1949)

v4.0.0

This is the official Vuex 4 release.

The focus for Vuex 4 is compatibility. Vuex 4 supports Vue 3, and it provides the exact same API as Vuex 3, so users can reuse their existing Vuex code with Vue 3.

There are a few breaking changes described in a later section, so please check them out.

You can find basic usage with both Option and Composition API in the example directory.

It's still released under next tag in NPM package as same as Vue 3. We're planning to remove next tag once Vue 3 is ready to remove it.

There have been a lot of contribution to make Vuex 4 stable. Thank you all for your very much appreciated help. It wouldn't have been possible without this wonderful Vue community!

Documentation

To check out docs, visit next.vuex.vuejs.org.

Breaking changes

Installation process has changed

To align with the new Vue 3 initialization process, the installation process of Vuex has changed.

To create a new store instance, users are now encouraged to use the newly introduced createStore function.

import { createStore } from 'vuex'
export const store = createStore({
state() {
return {
count: 1
}
}
})

Whilst this is not technically a breaking change, you may still use the new Store(...) syntax, we recommend this approach to align with Vue 3 and Vue Router 4.

... (truncated)

Changelog

Sourced from vuex's changelog.

4.1.0 (2022-10-14)

Vue Core Version Requirement Change

This release contains an important fix (#1883) that relies on the effectScope API from Vue core, which is only available in Vue 3.2+.

Bug Fixes

• build: node deprecated warning in export module (#2048) (397e9fb)
• getters being destroyed on component destroy (#1878) (#1883) (b2f851f)

4.0.2 (2021-06-17)

Bug Fixes

• devtools: fix no getters displayed on root module + better getters inspector (#1986) (bc20295)
• build: cjs build failing due to __VUE_PROD_DEVTOOLS__ defined (#1991) (#1992) (7151622)

4.0.1 (2021-05-24)

Features

• dx: add devtools integration (#1949)

4.0.0 (2021-02-02)

This is the official Vuex 4 release.

The focus for Vuex 4 is compatibility. Vuex 4 supports Vue 3, and it provides the exact same API as Vuex 3, so users can reuse their existing Vuex code with Vue 3.

There are a few breaking changes described in a later section, so please check them out.

You can find basic usage with both Option and Composition API in the example directory.

It's still released under next tag in NPM package as same as Vue 3. We're planning to remove next tag once Vue 3 is ready to remove it.

There have been a lot of contribution to make Vuex 4 stable. Thank you all for your very much appreciated help. It wouldn't have been possible without this wonderful Vue community!

Documentation

To check out docs, visit next.vuex.vuejs.org.

Breaking changes

Installation process has changed

To align with the new Vue 3 initialization process, the installation process of Vuex has changed.

... (truncated)

Commits

• d562224 release: v4.1.0
• 01f87f0 docs(zh): update zh docs from en docs (#2150)
• 75d20ec chore: delete unused import of shopping-cart example (#2156)
• e0ea5b8 docs: add note about Pinia becoming the new default
• 7651d50 docs(zh): wrong link to v3 docs in zh docs (#2129)
• dea4e36 docs: fix broken link to v3 docs (#2128)
• 747c488 chore: remove next references [ci skip]
• 29483f4 docs: update v3 links
• a03dc6a chore: update branch references
• eb52dfa docs: fix heading level (#2075)
• 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)