-
Notifications
You must be signed in to change notification settings - Fork 162
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
fix: Vue warning: Extraneous non-props attributes (data-v-inspector) #722
Comments
i also get this issue when using the devtools and with Shadcn-Vue, so im guessing its something with this module... if not i need to open a ticket in shadcn-vue. to recreate this issue, just install shadcn-vue in nuxt, and try using the components, even the example ones yield this error... note: the examples on stackblitz use vue, not nuxt. @antfu any hints? |
"I also encountered this problem. You can temporarily solve it by setting devtools: {
enabled: true,
componentInspector: false
} Link: #259 (comment)" |
Thanks for the suggestion. |
Any update on this? I like the inspector and I want to use it, but that warning fills my whole console. |
@jonasfroeller There is no update now. Just put this in your nuxt config file: |
Same issue. So, if Thank you! |
@HummingMind can you open a new issue about |
Sure. I'll open one later today. Edit: done |
It might caused by webfansplz/vite-plugin-vue-inspector#91 (suggested by @webfansplz). Downgraded it in |
@antfu Thank you! |
@HummingMind This might be shameful to ask, but please how do I downgrade? |
@neneodonkor you just need to upgrade to the latest version of the nuxt devtools. I fyou are on version 1.5.2, it already uses an older (downgraded) version of the vite-plugin-vue-inspector package. If you are using nuxt, you can run this: That should upgrade your pakcages to the latest version and it removes the lock file and node_modules before it reinstalls it: |
@HummingMind ok I installed Nuxt about two days ago. But how can check the version of Nuxt/DevTools? |
Windows: npm list --depth=1 | findstr @nuxt/devtools Linux: npm list --depth=1 | grep @nuxt/devtools |
@HummingMind Thanks for the assist. |
thx a lot for fixing it, this was so annoying ❤️❤️❤️ |
I still get this warning using
├── @nuxt/devtools-kit 1.5.2
|
@jonasfroeller I cannot open it because it was Nuxt Core member (antfu) that closed it. I suggest you open another one and make reference to this one. |
📚 What are you trying to do?
I got a warning after I upgraded for the previous version of Nuxt in my project. Although it is not a major bug, it would be nice to know where the issue is in my code. Maybe if someone could explain, it could be of help. I suspect it has to do with passing down props.
🔍 What have you tried?
No response
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered: