chore(deps): update optionaldependency vuex to v4 #728
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
|
WalkthroughThe changes involve updating the Changes
Sequence Diagram(s)sequenceDiagram
participant A as Application
participant B as Vuex 3.6.2
participant C as Vuex 4.1.0
A->>B: Initialize with Vuex 3.6.2
B-->>A: Provide state management
A->>C: Upgrade to Vuex 4.1.0
C-->>A: Provide enhanced state management
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (8)
- packages/blocks/package.json (1 hunks)
- packages/breadcrumb/package.json (1 hunks)
- packages/druxt/package.json (1 hunks)
- packages/menu/package.json (1 hunks)
- packages/router/package.json (1 hunks)
- packages/schema/package.json (1 hunks)
- packages/site/package.json (1 hunks)
- packages/views/package.json (1 hunks)
Additional comments not posted (8)
packages/schema/package.json (1)
48-48: LGTM! But verify compatibility with the new version ofvuex.The update to
vuexversion^4.1.0is necessary to keep dependencies current. However, this major version upgrade may introduce breaking changes that could affect the functionality of the application. Ensure that the application is compatible with the new version ofvuex.packages/breadcrumb/package.json (1)
51-51: LGTM! But verify compatibility with the new version ofvuex.The update to
vuexversion^4.1.0is necessary to keep dependencies current. However, this major version upgrade may introduce breaking changes that could affect the functionality of the application. Ensure that the application is compatible with the new version ofvuex.packages/blocks/package.json (1)
53-53: LGTM! But verify compatibility with the new version ofvuex.The update to
vuexversion^4.1.0is necessary to keep dependencies current. However, this major version upgrade may introduce breaking changes that could affect the functionality of the application. Ensure that the application is compatible with the new version ofvuex.packages/menu/package.json (1)
52-52: LGTM! But verify compatibility with the existing codebase.The
vuexdependency has been updated from^3.6.2to^4.1.0. Ensure that the codebase is compatible with the new version, as it introduces breaking changes and new features.The code changes are approved.
Run the following script to verify the compatibility of the updated dependency:
packages/router/package.json (1)
56-56: LGTM! But verify compatibility with the existing codebase.The
vuexdependency has been updated from^3.6.2to^4.1.0. Ensure that the codebase is compatible with the new version, as it introduces breaking changes and new features.The code changes are approved.
Run the following script to verify the compatibility of the updated dependency:
packages/views/package.json (1)
55-55: LGTM! But verify compatibility with the existing codebase.The
vuexdependency has been updated from^3.6.2to^4.1.0. Ensure that the codebase is compatible with the new version, as it introduces breaking changes and new features.The code changes are approved.
Run the following script to verify the compatibility of the updated dependency:
packages/site/package.json (1)
58-58: LGTM! But verify the dependency usage in the codebase.The
vuexdependency version is updated from^3.6.2to^4.1.0. Ensure that the codebase is compatible with the new version.The code changes are approved.
Run the following script to verify the dependency usage:
packages/druxt/package.json (1)
65-65: LGTM! But verify the dependency usage in the codebase.The
vuexdependency version is updated from^3.6.2to^4.1.0. Ensure that the codebase is compatible with the new version.The code changes are approved.
Run the following script to verify the dependency usage:
This PR contains the following updates:
^3.6.2->^4.1.0Release Notes
vuejs/vuex (vuex)
v4.1.0Compare Source
Vue Core Version Requirement Change
This release contains an important fix (#1883) that relies on the
effectScopeAPI from Vue core, which is only available in Vue 3.2+.Bug Fixes
4.0.2 (2021-06-17)
Bug Fixes
__VUE_PROD_DEVTOOLS__defined (#1991) (#1992) (7151622)4.0.1 (2021-05-24)
Features
v4.0.2Compare Source
Bug Fixes
__VUE_PROD_DEVTOOLS__defined (#1991) (#1992) (7151622)v4.0.1Compare Source
Features
v4.0.0Compare Source
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
exampledirectory.It's still released under
nexttag in NPM package as same as Vue 3. We're planning to removenexttag 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
createStorefunction.To install Vuex to a Vue instance, pass the store instance instead of Vuex.
Bundles are now aligned with Vue 3
The following bundles are generated to align with Vue 3 bundles:
vuex.global(.prod).js<script src="...">in the browser. Exposes the Vuex global.<script src="...">..prod.jsfiles for production.vuex.esm-browser(.prod).js<script type="module">.vuex.esm-bundler.jswebpack,rollupandparcel.process.env.NODE_ENVguards (must be replaced by bundler).vuex.cjs.jsrequire().Typings for
ComponentCustomPropertiesVuex 4 removes its global typings for
this.$storewithin Vue Component to solve issue #994. When used with TypeScript, you must declare your own module augmentation.Place the following code in your project to allow
this.$storeto be typed correctly:createLoggerfunction is exported from the core moduleIn Vuex 3,
createLoggerfunction was exported fromvuex/dist/loggerbut it's now included in the core package. You should import the function directly fromvuexpackage.Bug Fixes Included Since 4.0.0-rc.2
storeKey(4ab2947)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.