[Snyk] Upgrade vuex from 4.0.0-rc.2 to 4.1.0 #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade vuex from 4.0.0-rc.2 to 4.1.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: vuex
-
4.1.0 - 2022-10-14
-
4.0.2 - 2021-06-17
- devtools: fix no getters displayed on root module + better getters inspector (#1986) (bc20295)
- build: cjs build failing due to
-
4.0.1 - 2021-05-24
- dx: add devtools integration (#1949)
-
4.0.0 - 2021-02-02
import { createStore } from 'vuex'
import { createApp } from 'vue'
- For direct use with
- Global build is built as IIFE, and not UMD, and is only meant for direct use with
- Contains hard-coded prod/dev branches and the prod build is pre-minified. Use the
- For use with native ES module imports (including module supporting browsers via
- For use with bundlers such as
- Leaves prod/dev branches with
- Does not ship minified builds (to be done together with the rest of the code after bundling).
- For use in Node.js server-side rendering with
// vuex-shim.d.ts
- export missing
- fix tree shaking notworking in webpack bundle (#1906) (#1907) (aeddf7a)
-
4.0.0-rc.2 - 2020-11-25
- fix getters stop working when component is destroyed (#1884) (c3a695e)
- stop throwing an error on
- build: enable named esm module import on node.js >= 14 (4f4a909)
from vuex GitHub release notesrelease: v4.1.0
Bug Fixes
__VUE_PROD_DEVTOOLS__defined (#1991) (#1992) (7151622)Features
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.export const store = createStore({
state() {
return {
count: 1
}
}
})
To install Vuex to a Vue instance, pass the store instance instead of Vuex.
import { store } from './store'
import App from './App.vue'
const app = createApp(App)
app.use(store)
app.mount('#app')
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:import { ComponentCustomProperties } from 'vue'
import { Store } from 'vuex'
declare module '@ vue/runtime-core' {
// Declare your own store states.
interface State {
count: number
}
interface ComponentCustomProperties {
$store: Store<State>
}
}
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)Bug Fixes
hasModulewhen parent does not exists (#1850) (f76d72d)Features
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs