to app.vue\n8. start the project via npm run dev\n9. open created localhost link in browser\n[Minimal reproduction link](https://stackblitz.com/edit/github-dksvnc-l71vra)\n\n### Describe the bug\n\nRunning in development mode (and shortly seems to be an issue for production build also) and opening app in browser leads to error in Vue Router. You can still get it work by redirecting to other path by clicking the link to another page, but the error will return after page refresh which is extremely uncomfartable for local work\n\nSetting ssr: false in nuxt.config.ts solves this issue, but we need ssr: true for the project\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue Router warn]: uncaught error during route navigation:\nCannot destructure property '__webpack_ids__' of 'data' as it is undefined.\n\n at installChunk (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Promise.all (index 0)\n at setup (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at applyPlugin (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at executePlugin (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at applyPlugins (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at createNuxtAppServer (node_modules\\nuxt\\dist\\core\\runtime\\nitro\\renderer.js:525:1)\n at async Object.renderToString (/D:/dev/text-nuxt/node_modules/vue-bundle-renderer/dist/runtime.mjs:173:19)\n```",[2903,2906,2909],{"name":2904,"color":2905},"bug","d73a4a",{"name":2907,"color":2908},"webpack","650C6F",{"name":2910,"color":2911},"❗ p4-important","D93F0B",30165,"nuxt","open","[Vue Router warn]: uncaught error during route navigation when building with webpack","2024-12-17T06:37:23Z","https://github.com/nuxt/nuxt/issues/30165",0.66423744,{"description":2920,"labels":2921,"number":2434,"owner":2913,"repository":2922,"state":2923,"title":2924,"updated_at":2925,"url":2926,"score":2927},"When using with Nuxt rc 11, I'm getting the following warnings in SSR.\r\nInside \u003Cclient-only> the warning is not triggered. Warning is triggered once per component usage.\r\n\r\nI'm using it as expexted:\r\n\r\n```\r\n\u003CIcon name=\"ic:baseline-search\" />\r\n```\r\n\r\nIs there something that should be done, besides using \u003Cclient-only>?\r\n\r\n\r\nHere's what I'm being warned (Index.vue page)\r\n\r\n```\r\n[Vue warn]: The `compilerOptions` config option is only respected when using a build of Vue.js that includes the runtime compiler (aka \"full build\"). Since you are using the runtime-only build, `compilerOptions` must be passed to `@vue/compiler-dom` in the build setup instead.\r\n- For vue-loader: pass it via vue-loader's `compilerOptions` loader option.\r\n- For vue-cli: see https://cli.vuejs.org/guide/webpack.html#modifying-options-of-a-loader\r\n- For vite: pass it via @vitejs/plugin-vue options. See https://github.com/vitejs/vite/tree/main/packages/plugin-vue#example-for-passing-options-to-vuecompiler-dom \r\n at \u003CIcon name=\"mdi:qrcode-scan\" > \r\n at \u003CIndex class=\"relative h-screen content-border pt-14\" onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C Proxy {__v_skip: true} > > \r\n at \u003CAnonymous key=\"/\" routeProps= {Component: {…}, route: {…}} pageKey=\"/\" ... > \r\n at \u003CBaseTransition mode=\"out-in\" appear=false persisted=false ... > \r\n at \u003CTransition name=\"page\" mode=\"out-in\" > \r\n at \u003CRouterView name=undefined route=undefined class=\"relative h-screen content-border pt-14\" > \r\n at \u003CNuxtPage class=\"relative h-screen content-border pt-14\" > \r\n at \u003CDefault > \r\n at \u003CAsyncComponentWrapper > \r\n at \u003CBaseTransition mode=\"out-in\" appear=false persisted=false ... > \r\n at \u003CTransition name=\"layout\" mode=\"out-in\" > \r\n at \u003CAnonymous> \r\n at \u003CApp key=1 > \r\n at \u003CNuxtRoot>\r\n```",[],"icon","closed","Warnings when in use with Nuxt rc-11","2022-09-29T12:33:30Z","https://github.com/nuxt/icon/issues/16",0.45237926,{"description":2929,"labels":2930,"number":2934,"owner":2913,"repository":2913,"state":2923,"title":2935,"updated_at":2936,"url":2937,"score":2938},"Hello, I am trying to use Vue-clip plugin in my Nuxt project. (http://vueclip.adonisjs.com)\r\n\r\nThis is my `nuxt.config.js` configuration file:\r\n\r\n`...`\r\n`build: {`\r\n ` vendor: ['axios', 'vue-clip']`\r\n ` },`\r\n` plugins: [`\r\n ` { src: '~plugins/vue-clip.js', ssr: false }`\r\n ` ],`\r\n`...`\r\n\r\nAnd this is my `~plugins/vue-clip.js` file:\r\n\r\n`import Vue from 'vue'`\r\n`import VueClip from 'vue-clip'`\r\n`Vue.use(VueClip)`\r\n\r\nThis is the error I have on render:\r\n\r\n[Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.\r\n\r\nDo you know where it could come from ?\r\n\r\nThe plugin itself has, in the `webpack.config.js`\r\n\r\n`resolve: {\r\n alias: {\r\n vue: 'vue/dist/vue.js'\r\n }\r\n }`\r\n\r\nShould I use the same alias in the `nuxt.config.js` file ?\r\n\r\nThank you very much for your help!",[2931],{"name":2932,"color":2933},"2.x","d4c5f9",1142,"[Vue warn]: You are using the runtime-only build of Vue...","2023-01-18T15:40:52Z","https://github.com/nuxt/nuxt/issues/1142",0.6438725,{"labels":2940,"number":2941,"owner":2913,"repository":2913,"state":2923,"title":2942,"updated_at":2943,"url":2944,"score":2945},[],13114,"Hydration error for redirect route plugin","2023-01-19T16:47:39Z","https://github.com/nuxt/nuxt/issues/13114",0.6475206,{"labels":2947,"number":2948,"owner":2913,"repository":2913,"state":2923,"title":2942,"updated_at":2949,"url":2950,"score":2945},[],13185,"2023-01-19T16:48:28Z","https://github.com/nuxt/nuxt/issues/13185",{"description":2952,"labels":2953,"number":2957,"owner":2913,"repository":2913,"state":2923,"title":2958,"updated_at":2959,"url":2960,"score":2961},"\r\n**(Need Help) Encountering Warnings When Using Nuxt3 + shadcnUI and Unsure How to Fix Them**\r\n\r\nHere’s the component code:\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { DialogRoot, VisuallyHidden } from \"radix-vue\";\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv id=\"index-side-bar\">\r\n \u003Cslot />\r\n \u003CSheet :default-open=\"true\">\r\n \u003CSheetContent :side=\"'left'\" class=\"outline-0 p-0 w-[240px] z-[99999]\">\r\n \u003CVisuallyHidden>\r\n \u003CSheetHeader>\r\n \u003CSheetTitle>dialog\u003C/SheetTitle>\r\n \u003CSheetDescription>description\u003C/SheetDescription>\r\n \u003C/SheetHeader>\r\n \u003C/VisuallyHidden>\r\n \u003Cdiv style=\"width: 100%; height: 100vh; display: flex; flex-direction: column;\">\r\n \u003C!-- Header -->\r\n \u003Cdiv class=\"w-full h-[56px] flex items-center sm:h-[48px]\">\r\n \u003Cdiv class=\"w-full h-[56px] flex items-center ml-[14px] sm:ml-[16px]\">\r\n \u003Cdiv class=\"w-10 h-10 flex items-center justify-center sm:hidden\">\r\n \u003C!-- SVG Icon Placeholder -->\r\n \u003C/div>\r\n \u003Cdiv class=\"w-[120px] h-[56px] sm:w-auto sm:h-[48px]\" style=\"display: flex; justify-content: center; align-items: center;\">\r\n \u003Cdiv class=\"w-[94px] h-[30px]\">\r\n \u003C!-- Logo Placeholder -->\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C!-- Footer -->\r\n \u003Cdiv class=\"sidebar_toolbar\">\r\n \u003CSheetClose class=\"outline-0\">\r\n \u003CNuxtLayout name=\"tab-toolbar-nav-menu\" />\r\n \u003C/SheetClose>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/SheetContent>\r\n \u003C/Sheet>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nShadcnUI Sheet.vue:\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { DialogRoot, type DialogRootEmits, type DialogRootProps, useForwardPropsEmits } from 'radix-vue';\r\n\r\nconst props = defineProps\u003CDialogRootProps>();\r\nconst emits = defineEmits\u003CDialogRootEmits>();\r\nconst forwarded = useForwardPropsEmits(props, emits);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CDialogRoot v-bind=\"forwarded\">\r\n \u003Cslot />\r\n \u003C/DialogRoot>\r\n\u003C/template>\r\n```\r\n\r\n**The warning message:**\r\n\r\n```text\r\n[Vue warn]: Extraneous non-props attributes (data-v-e01f9c95) were passed to component but could not be automatically inherited because component renders fragment or text root nodes.\r\n at \u003CDialogRoot defaultOpen=true onUpdate:open=fn data-v-e01f9c95=\"\" >\r\n at \u003CSheet default-open=true >\r\n at \u003CSideBar ref=Ref\u003C undefined > >\r\n```\r\n\r\nThis warning has appeared multiple times and only occurs on the server side. No warnings appear on the client side.\r\n\r\nThrough testing, I found that switching to the `DialogRoot` component eliminates the warnings. The warnings reappear when using the `Sheet` component.\r\n\r\nHere’s the alternative component:\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { DialogRoot, VisuallyHidden } from \"radix-vue\";\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv id=\"index-side-bar\">\r\n \u003Cslot />\r\n \u003CDialogRoot :default-open=\"true\">\r\n \u003CSheetContent :side=\"'left'\" class=\"outline-0 p-0 w-[240px] z-[99999]\">\r\n \u003CVisuallyHidden>\r\n \u003CSheetHeader>\r\n \u003CSheetTitle>dialog\u003C/SheetTitle>\r\n \u003CSheetDescription>description\u003C/SheetDescription>\r\n \u003C/SheetHeader>\r\n \u003C/VisuallyHidden>\r\n \u003Cdiv style=\"width: 100%; height: 100vh; display: flex; flex-direction: column;\">\r\n \u003C!-- Header -->\r\n \u003Cdiv class=\"w-full h-[56px] flex items-center sm:h-[48px]\">\r\n \u003Cdiv class=\"w-full h-[56px] flex items-center ml-[14px] sm:ml-[16px]\">\r\n \u003Cdiv class=\"w-10 h-10 flex items-center justify-center sm:hidden\">\r\n \u003C!-- SVG Icon Placeholder -->\r\n \u003C/div>\r\n \u003Cdiv class=\"w-[120px] h-[56px] sm:w-auto sm:h-[48px]\" style=\"display: flex; justify-content: center; align-items: center;\">\r\n \u003Cdiv class=\"w-[94px] h-[30px]\">\r\n \u003C!-- Logo Placeholder -->\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C!-- Footer -->\r\n \u003Cdiv class=\"sidebar_toolbar\">\r\n \u003CSheetClose class=\"outline-0\">\r\n \u003CNuxtLayout name=\"tab-toolbar-nav-menu\" />\r\n \u003C/SheetClose>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/SheetContent>\r\n \u003C/DialogRoot>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n**When using DevTools**, the same warning occurs, similar to the server-side warning, but it doesn’t appear on the client side:\r\n\r\n```text\r\n[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.\r\n at \u003CDialogRoot default-open=true data-v-inspector=\"layouts/index/SideBar.vue:16:7\" >\r\n at \u003CSideBar data-v-inspector=\"app.vue:4:7\" ref=Ref\u003C undefined > >\r\n at \u003CLayoutLoader key=\"index-side-bar\" layoutProps= { 'data-v-inspector': 'app.vue:4:7',\r\n```\r\n\r\nI have already disabled DevTools with `componentInspector: false`.\r\n\r\nGitHub link: [Nuxt DevTools Issue #722](https://github.com/nuxt/devtools/issues/722).\r\n",[2954],{"name":2955,"color":2956},"pending triage","E99695",29002,"(Need Help) Encountering Warnings When Using Nuxt3 + shadcnUI and Unsure How to Fix Them","2024-09-17T08:13:28Z","https://github.com/nuxt/nuxt/issues/29002",0.6550973,{"description":2963,"labels":2964,"number":2975,"owner":2913,"repository":2913,"state":2923,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: pnpm@8.6.10\r\n- Builder: vite\r\n- User Config: devtools, imports, modules, css, svgo, i18n, headlessui, image, components, extends, runtimeConfig, linkChecker, googleFonts, build, vite\r\n- Runtime Modules: @nuxtjs/eslint-module@4.1.0, @pinia/nuxt@0.4.11, @nuxtjs/i18n@8.0.0-beta.13, nuxt-svgo@3.4.0, nuxt-headlessui@1.1.4, @nuxt/image@1.0.0-rc.1, nuxt-typed-router@3.2.5, @formkit/nuxt@0.17.5, @nuxtjs/tailwindcss@6.8.0, nuxt-icon@0.4.2, @nuxtjs/google-fonts@3.0.2, @vueuse/nuxt@10.3.0\r\n- Build Modules: -\n\n### Reproduction\n\n[Stackblitz reproduction link](https://stackblitz.com/edit/github-6gkd6t?file=app.vue)\r\n\r\n1. Add plugin exactly the same as in [docs about providing helpers](https://nuxt.com/docs/guide/directory-structure/plugins#automatically-providing-helpers)\r\n2. Use `const { $hello } = useNuxtApp()` in .client component\r\n3. Look at the warn in the browser console - `[Vue warn]: setup() return property \"$hello\" should not start with \"$\" or \"_\" which are reserved prefixes for Vue internals. `\n\n### Describe the bug\n\nI'm getting [Vue warn]: setup() return property \"$hello\" should not start with \"$\" or \"_\" which are reserved prefixes for Vue internals when using .client component.\r\nWhen using \"normal\" component (without .client extension) there is no warn and everything works as expected\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2965,2968,2969,2972],{"name":2966,"color":2967},"3.x","29bc7f",{"name":2904,"color":2905},{"name":2970,"color":2971},"🔨 p3-minor","FBCA04",{"name":2973,"color":2974},"✨ good reproduction","fbca04",22435,"I'm getting [Vue warn]: setup() return property \"$hello\" should not start with \"$\" or \"_\" which are reserved prefixes for Vue internals when using .client component","2024-01-02T21:04:59Z","https://github.com/nuxt/nuxt/issues/22435",0.655383,{"labels":2981,"number":2984,"owner":2913,"repository":2913,"state":2923,"title":2942,"updated_at":2985,"url":2986,"score":2987},[2982,2983],{"name":2966,"color":2967},{"name":2955,"color":2956},13054,"2023-01-19T16:57:31Z","https://github.com/nuxt/nuxt/issues/13054",0.65775573,{"description":2989,"labels":2990,"number":2993,"owner":2913,"repository":2913,"state":2923,"title":2994,"updated_at":2995,"url":2996,"score":2997},"### Environment\n\nNuxi 3.0.0-rc.10\r\nRootDir: /sandbox\r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v14.19.3`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://codesandbox.io/s/jolly-sky-uz9ovm?file=/pages/index.vue\r\n\r\nHere's a snippet of the juicy bit:\r\n```\r\n\u003CNuxtLink v-slot=\"{ href }\" to=\"/foo\" custom>\r\n \u003Ca :href=\"href\">Here's a link\u003C/a>\r\n\u003C/NuxtLink>\r\n```\n\n### Describe the bug\n\nWhen using a NuxtLink component with custom attribute, a warning is logged.\n\n### Additional context\n\nIn RC 8 it was working fine, my suspicion is that the new link prefetching feature is to blame.\r\n\r\nSuspicious line of code: https://github.com/nuxt/framework/blob/v3.0.0-rc.10/packages/nuxt/src/app/components/nuxt-link.ts#L229\r\n\r\nMaybe worth to mention, a workaround is to use vue router's RouterLink component directly instead of NuxtLink\n\n### Logs\n\n```shell\n[Vue warn]: Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text root nodes.\n```\n",[2991,2992],{"name":2966,"color":2967},{"name":2904,"color":2905},14897,"NuxtLink with custom attribute causes vue warning in RC10","2023-01-19T17:42:08Z","https://github.com/nuxt/nuxt/issues/14897",0.65814716,{"description":2999,"labels":3000,"number":3009,"owner":2913,"repository":2913,"state":2923,"title":3010,"updated_at":3011,"url":3012,"score":3013},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25196\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CClientOnly>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n \u003C/ClientOnly>\r\n\u003C/template>\r\n```\r\n\r\n### Describe the bug\r\n\r\nWhen using a `\u003CClientOnly>` component around the `App.vue` (only SSR the app shell), the NuxtLayout warning will appear even though the component is used.\r\n\r\n### Additional context\r\n\r\nRelated: https://github.com/nuxt/nuxt/issues/24912\r\n\r\n### Logs\r\n\r\n_No response_",[3001,3002,3005,3006],{"name":2966,"color":2967},{"name":3003,"color":3004},"dx","C39D69",{"name":2904,"color":2905},{"name":3007,"color":3008},"🍰 p2-nice-to-have","0E8A16",25196,"`\u003CNuxtLayout /> component has not been used.` Warning when using `\u003CClientOnly>` in `app.vue`","2024-02-09T20:33:36Z","https://github.com/nuxt/nuxt/issues/25196",0.66173124,["Reactive",3015],{},["Set"],["ShallowReactive",3018],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fD83-zCcOWm8segtWEdHvcAwJ9RpLBvtHYu_Ax5d70EQ":-1},"/nuxt/scripts/16"]