5.0.0-beta.3
Chrom 69 / El Capitan
Just go to my web page in dev mode with the vue-devtools enabled.
Everything to work like it did in version 4.
Get a javascript error in a getter because it is called before initialization.
This might be more of a clue about what is going on. In my app, one of the first things I do is set the router property in my state. I do that here:
new Vue({
...
created: function() {
store.dispatch('setRouter', router);
}
With the new version of the vuetools, rootGetters.router is null and causes a crash in one of my getters and the entire initialization stops.
@simplesmiler Could this come from the early Vuex clone?
FWIW I was having a similar problem. Hard crash could not load my site when vuex hit this code devtoolHook.emit('vuex:init', store); I disabled vue-devtools and the site worked fine. Strangely I re-enabled vue-devtools and the site still works.
I'm seeing the same thing using vue-devtools 5.0.0-beta.3 and Chrome 69.0.3497.100. Vuex getter rootState.route is undefined.
I'm also intermittently seeing another error: __VUE_DEVTOOLS_UID__ of undefined in vue-devtools on the 4.1.5 beta version
Hey, I've got the same problem here. Just upgrade to v5beta, and got "Cannot read property 'getters' of undefined" in Chrome JS console.

Then I went back to v4 of Vue.js devTools and everything works fine.
Workaround: I got it to work by removing the Vue devtools plugin(s) and reinstalling them on the latest (fresh install) version of Chrome.
I am facing vue devtools crashing problem even without using vuex. I an hour of coding it crashes atleast 8-10 times.
I'm getting an error with the new dev tools using Vuex and vuex-router-sync.
Its crashing on a getter:
inBookingView(state) {
return state.route.name === 'bookings';
}
with an error: Cannot read property 'name' of undefined,
it works fine with Vue devtools 4.
In my case:
Uncaught TypeError: Cannot read property '_modulesNamespaceMap' of undefined
at getModuleByNamespace (app.js?id=411dba539e4fd3da7533:174959)
at Vue.mappedGetter (app.js?id=411dba539e4fd3da7533:174892)
at Watcher.get (app.js?id=411dba539e4fd3da7533:166214)
at Watcher.evaluate (app.js?id=411dba539e4fd3da7533:166321)
at Proxy.computedGetter (app.js?id=411dba539e4fd3da7533:166579)
at l (<anonymous>:1:1915)
at l (<anonymous>:1:1912)
at l (<anonymous>:1:1912)
at i (<anonymous>:1:2190)
at Object.n.once.t (<anonymous>:1:2698)
I have the same described here: https://github.com/vuejs/vue-devtools/issues/775
This is a big thing for me, maybe getters could be collapsed and disabled by default, and call them all on expand.
Workaround: I got it to work by removing the Vue devtools plugin(s) and reinstalling them on the latest (fresh install) version of Chrome.
This workaround not worked for me.
I'm on version 4.1.5 beta (Ubuntu 16, Chrome 70)
Duplicate of #775