Vue-devtools: Cannot read property 'type' of null

[nasirouwagana]

OS : Ubuntu 16.04
Chrome : 63.0.3239.84
vue : 2.5.13
vuex : 3.0.1
vue-devtools: 4.0.0

No content is appeared at right side, when I click on a component to inspect it.
After I click on a component to inspect it, there are also a lot of errors in my console.

Please look at these two images below.

[MinimiseNZ]

Same issues here. Is affecting the functionality of entire app. Functionality is restored only when vue-devtools is uninstalled

[Nikolay200669]

+1
This problem also in Firefox

[ankurk91]

I have the same error.
Version 63.0.3239.108 (Official Build) (64-bit)

I uninstalled the extension and re-installed but the issue remain same.
This is happening when we select a child component in tree view.

[patrikengborg]

I have the same issue.

[mariomka]

I have the same issue

OS : macOS 10.13.2
Chrome : 63.0.3239.132
vue : 2.5.9
vuex : 2.5.0
vue-devtools: 4.0.0

[DannyHinshaw]

Same issue here.

Appears to be solved by checking 'Allow access to file URLs' on extension' checkbox on the chrome extension.

Specifically, my error was related to vue-router whenever I changed routes, though not every time... Unfortunately, I don't have the time to dig further at this point, but hopefully that helps someone.

Edit: Nervermind, there error has returned.

[einnar82]

+1
Also in npm run build

[ArjenNZ]

This seems to be an issue concerning https://vuejs.org/v2/api/#provide-inject . For me, vee-validate was the problem.

Fix: set Component Injections to false, and inject the validator in the specific component. Hope this helps anybody with the errors in vee-validate.

[nasirouwagana]

Exactly @ArjenNZ, you are right. If I desactivate vee-validate, vue-devtools works properly.
I forgot to mention earlier I have used vee-validate : 2.0.2.

[mariomka]

@ArjenNZ yep! Devtools works well, disabling vee-validate.

[sigfriedseldeslachts]

You can fix the issue by placing an input or so and add v-validate attribute on it. This however is not a permanent solution, and not a good one either. But it get's the job done, meanwhile just wait for an update.

<input type="hidden" v-validate="'required'">

[groenroos]

Same issue here; disabling v-validate makes the problems go away, but obviously that's not a real fix.

[logaretm]

I've tagged 2.0.3 with a fix for the issue, could you guys upgrade vee-validate and test it?

[nasirouwagana]

@logaretm vue-devtools now works. Thank for your awesome work.

[groenroos]

I've got vue-devtools 4.0.1 and vee-validate 2.0.3, and the issue seems to have gone away!

[sigfriedseldeslachts]

Issue has been fixed in vee-validate 2.0.3

[thomassjogren]

@logaretm Thanks for the fast fix.

[Akryum]

This shouldn't happen again with #523.

[eric-gm]

Yep, npm install --save [email protected] fixes this issue! Thanks @logaretm

[Mouvedia]

I am stuck with 2.0.0-rc.25 due to the breaking changes in rc 26 that are too numerous.

[kaungmyatlwin]

This is also happening on Element UI 1.4.x with Vue 2.4.x.

[Akryum]

Try this branch: https://github.com/Akryum/vue-devtools/tree/types-improvements

[sellou]

Any clues how to resolve this issue with vuelidate ?
Thanks

[sigfriedseldeslachts]

@sellou use vee-validate. The issue has been solved there.

Sorry. I thought you meant vee-validate (removed previous message).