Skip to content
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

Nuxt 3.13.2 dev server logs noisy Vue warnings from extraneous non-prop attribute (data-v-inspector) #731

Closed
deleteme opened this issue Sep 17, 2024 · 2 comments

Comments

@deleteme
Copy link

Environment

  • Operating System: Darwin
  • Node Version: v18.15.0
  • Nuxt Version: 3.13.2
  • CLI Version: 3.13.2
  • Nitro Version: 2.9.7
  • Package Manager: yarn@3.6.1
  • Builder: -
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Reproduction

https://stackblitz.com/edit/github-psuobu

Describe the bug

Nuxt is applying a data-v-inspector prop to every component, though none expect it.

Vue 3 logs the following to the server console in development, plus a Vue component tree, which can be very noisy and make it difficult to find more important output.

[Vue warn]: Extraneous non-props attributes (data-v-inspector) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. 

Additional context

  • Some Vue components do not render DOM nodes themselves, but instead act as wrappers of some sort, and delegate rendering through to a slot. This kind of component is subject to the Vue extraneous props warning.
  • A workaround is to disable devtools entirely or set devtools: { enabled: true, componentInspector: true }, in the nuxt config.

Logs

No response

Copy link

stackblitz bot commented Sep 17, 2024

Fix this issue in StackBlitz Codeflow Start a new pull request in StackBlitz Codeflow.

@danielroe danielroe transferred this issue from nuxt/nuxt Sep 17, 2024
@antfu
Copy link
Member

antfu commented Sep 23, 2024

Duplicated #722

@antfu antfu closed this as not planned Won't fix, can't repro, duplicate, stale Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants