-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'type' of null #499
Comments
Same issues here. Is affecting the functionality of entire app. Functionality is restored only when vue-devtools is uninstalled |
+1 |
I have the same issue. |
I have the same issue OS : macOS 10.13.2 |
Same issue here.
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. |
+1 |
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. |
Exactly @ArjenNZ, you are right. If I desactivate vee-validate, vue-devtools works properly. |
@ArjenNZ yep! Devtools works well, disabling vee-validate. |
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'"> |
Same issue here; disabling v-validate makes the problems go away, but obviously that's not a real fix. |
I've tagged 2.0.3 with a fix for the issue, could you guys upgrade |
@logaretm vue-devtools now works. Thank for your awesome work. |
I've got vue-devtools 4.0.1 and vee-validate 2.0.3, and the issue seems to have gone away! |
Issue has been fixed in vee-validate 2.0.3 |
@logaretm Thanks for the fast fix. |
This shouldn't happen again with #523. |
Yep, |
I am stuck with 2.0.0-rc.25 due to the breaking changes in rc 26 that are too numerous. |
fixed issue with vue dev-tools (vuejs/devtools-v6#499)
This is also happening on Element UI 1.4.x with Vue 2.4.x. |
Any clues how to resolve this issue with vuelidate ? |
@sellou use vee-validate. The issue has been solved there. Sorry. I thought you meant vee-validate (removed previous message). |
fixed issue with vue dev-tools (vuejs/devtools-v6#499)
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.
The text was updated successfully, but these errors were encountered: