rtucek/vue-query-builder

reactiveInject error

Opened this issue · 2 comments

dokudoki commented

I'm having this issue when try to follow the docs. Using Vue 2.6.12

vue.esm.js?a026:628 [Vue warn]: Error in nextTick: "TypeError: Cannot use 'in' operator to search for '__reactiveInject__' in undefined" vue.esm.js?a026:1897 TypeError: Cannot use 'in' operator to search for '__reactiveInject__' in undefined at resolveInject (vue.esm.js?aba4:4649:1) at initInjections (vue.esm.js?aba4:4619:1) at Vue._init (vue.esm.js?aba4:4710:1) at new QueryBuilder (vue.esm.js?aba4:5836:1) at createComponentInstanceForVnode (vue.esm.js?a026:3292:1) at init (vue.esm.js?a026:3123:1) at createComponent (vue.esm.js?a026:5989:1) at createElm (vue.esm.js?a026:5936:1) at createChildren (vue.esm.js?a026:6064:1) at createElm (vue.esm.js?a026:5965:1)

DavidHarvey commented

@rtucek I am also receiving this error. Tested on each version of Vue from 2.6.11 to 2.6.14.

Reproduced using the minimal configuration setup in an existing project built with Nuxt via webpack. Error does not occur in the code sandbox example for the same setup provided in the docs.

TypeError: Cannot use 'in' operator to search for '__reactiveInject__' in undefined
    at resolveInject (vue.runtime.esm.js?17a6:4261:1)
    at initInjections (vue.runtime.esm.js?17a6:4231:1)
    at Vue._init (vue.runtime.esm.js?17a6:5690:1)
    at new QueryBuilder (vue.runtime.esm.js?17a6:5826:1)
    at createComponentInstanceForVnode (vue.runtime.esm.js?2b0e:3283:1)
    at init (vue.runtime.esm.js?2b0e:3114:1)
    at createComponent (vue.runtime.esm.js?2b0e:5978:1)
    at createElm (vue.runtime.esm.js?2b0e:5925:1)
    at createChildren (vue.runtime.esm.js?2b0e:6053:1)
    at createElm (vue.runtime.esm.js?2b0e:5954:1)
rtucek commented

@dokudoki and @DavidHarvey sorry, for my late reply.

Unfortunately, I can't reproduce your issue (not in codesandbox.io nor locally).

For instance, the tip of the main branch of this repo already uses v2.6.14 and similar, I took the first intro example from the docs and upgrade to v2.6.14 without any issues at all.

Could you provide me some concrete code to reproduce it?