-
Notifications
You must be signed in to change notification settings - Fork 163
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: WARN [Vue warn]: Extraneous non-props attributes (data-v-14ce88ff) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. #745
Comments
I will try to reproduce this in stackblitz, but I do not have much time rn.
I guess that is actually the fix. Upgrading pnpm. :/ |
Hi @jonasfroeller, could you still meet this issue in the latest version? |
I just tried the newest Nuxt version (using I tried pnpm and I stepped away for a few minutes to grab something to eat, and when I came back, the install had crashed. I encountered a new error, which seems odd to me. [15:48:16] ERROR require() of ES Module D:\xxx\node_modules\.pnpm\unplugin-vue-router@0.10.8_rollup@4.27.4_vue-router@4.5.0_vue@3.5.13_typescript@5.7.2___vue@3.5.13_typescript@5.7.2_\node_modules\unplugin-vue-router\dist\chunk-6F4PWJZI.js not supported.
chunk-6F4PWJZI.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
Instead either rename chunk-6F4PWJZI.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in \\?\D:\xxx\node_modules\.pnpm\unplugin-vue-router@0.10.8_rollup@4.27.4_vue-router@4.5.0_vue@3.5.13_typescript@5.7.2___vue@3.5.13_typescript@5.7.2_\node_modules\unplugin-vue-router\package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
ELIFECYCLE Command failed with exit code 1. at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at async loadNuxt (/D:/xxx/node_modules/.pnpm/@nuxt+kit@3.14.1592_magicast@0.3.5_rollup@4.27.4/node_modules/@nuxt/kit/dist/index.mjs:2632:37) |
@jonasfroeller |
@Iran-110 Yes. A few times. Is there any other solution instead of making that part global? |
🐛 The bug
🛠️ To reproduce
#722 (comment)
🌈 Expected behavior
No warning, if I do not have devtools enabled.
No warning at all, since this should be fixed (#722 (comment)).
ℹ️ Additional context
I still get this warning using
ShadcnTooltipProvider
(yes, I am using the latest versions of everything). The weird thing is, that I even disabled devtools and componentInspector in my nuxt.config.ts.├── @nuxt/devtools-kit 1.5.2
├── @nuxt/devtools 1.5.2
├── @nuxt/devtools-kit 1.5.2
The text was updated successfully, but these errors were encountered: