J
@s-molinari said in how can I use vuex-electron with quasar?:
Did you see the bit about adding the store to the plugin as a way to initialize the plug-in? Not all plug-ins allow for this, but it’s supposed to be a method to get the plug-in “injected” after the store is created. Something like:
import { createPersistedState, createSharedMutations } from 'vuex-electron'
export default ({ router, store, Vue }) => {
createPersistedState(store)
createSharedMutations(store)
}
It’s a wild guess on my part.
Scott
ooh no, that’s a good thing to investigate! I’m sort of at a point now where everything has been refactored to not use the store via the main process so it’s sort of a moot point, but that could well be a solution should other people have problems in future (assuming that it doesn’t quibble about electron since the event-pipeline hasn’t reached loading that at the point at which you create the boot).
@metalsadman yeah I was defining said store in my electron-main as specified in the instructions. I suspect the actions wont work if you don’t have createSharedMutations().
