Bug in vuex & vuex-router-sync: rawGetter is not a function

[xiaocode]

When click the route-link to another component, this error will show. I found it happen at vuex 2.0.0-rc.5 dist/index.js line 458 "store._wrappedGetters[getterKey]". When the getterKey is "default", this is an Object, not a Function. I don't know it is my problem or the bug.

[LinusBorg]

Hello @xiaocode,

thank you for your filing this issue.

Please follow the guidelines on how to report an issue. In particular, provide an example on www.jsfiddle.net (or a similar service) that reproduces the problem.

Thank you.

[LinusBorg]

Closing for inactivity

[pelletiermaxime]

Just ran into the same issue. Not sure I'm going to have the time to post an example anytime soon because my code isn't open source :/

[pelletiermaxime]

Restarting my browser seems to have fixed the bug. Clearing the cache wasn't enough.

[codeofsumit]

got the same issue. Restarting did not help.
Can't provide / create a isolated test case right now, sorry.

[pelletiermaxime]

It seems to appear when I use the chrome devtools with the vue plugin. Everything works fine in Firefox.

[LinusBorg]

Please provide:

• exact versions (Vue, vue-router, vuex, vuex-router-sync),
• a reproduction
• if you cant reproduce it on jsfiddle, at least explain exctly when this error shows up.
  • What are you doing in that moment?
  • Which link are you clicking?
  • What does the template and route config look like?

[codeofsumit]

I'll give it a shot.

vue 2.0.0-rc.5.
vue-router 2.0.0-rc.4
vuex 2.0.0-rc.5
vuex-router-sync 3.0.0

I found that in my case it shows up when I click on a specific component, here it's VLocationResults:

The VLocationResults component looks like this:

import store from './../../store';

export default {
  mixins: [
  ],
  props: {
  },
  data() {
    return {
      loc: store, // <-- problem HERE
    };
  },
};

I'm assuming because store is some kind of circular structure or something. Removing that and assigning proper data like store.state.dataProperty makes everything work fine.

So I guess it's some wrong/invalid(?) data return that causes this.

I'm a total beginner in vue so I don't know if that is actually invalid.

Hope that helps.

[LinusBorg]

Hi @codeofsumit

Thanks for looking into this!

Yes, you should defnitely not add a vuex store to the local state of a component. If everything works fine for you when you don't do that, I would not consider this a bug.

So I'll hope that @pelletiermaxime can offer some additional insight.

[codeofsumit]

@LinusBorg Of course I changed that property 😀
I did not know that this was not allowed. As I said I'm a total beginner and I thought the vue dev tools, or vue itself would tell me that I do something wrong instead of an "internal error" like that.
Most other scenarios are handled with error-messages that help me find the problem.

[async0x42]

I'm having the rawGetter error as well, with Chrome and devtools. I only import the store for the main app, and in no other components, but if I keep devtools open while loading some routes, it always throws this rawGetter exception.

vuex-router-sync 3.0.0
vue-2.0.0-rc.6
vuex-2.0.0-rc.5

[ktsn]

Hmm, I can't reproduce in my machine.
Can you guys provide the stack trace of the error?