\r\n```\r\n\r\n\r\nthe browser console throws following warning:\r\n\r\n```\r\nExtraneous non-emits event listeners (pointerenter, focus) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the \"emits\" option. \r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2867,2870,2873],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"pages","00DFB5",{"name":2874,"color":2875},"馃敤 p3-minor","FBCA04",28732,"closed","NuxtLink with custom directive is throwing console warning","2024-08-28T11:32:00Z","https://github.com/nuxt/nuxt/issues/28732",0.6565616,{"description":2883,"labels":2884,"number":2891,"owner":2857,"repository":2857,"state":2877,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### Environment\n\nNuxi 3.2.2 \r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.14.1`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `components`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nReproduce Link: https://stackblitz.com/edit/github-tznxrd\r\n\r\n1. npx nuxi init demo\r\n2. cd demo\r\n3. npm install\r\n4. mkdir -p components/layouts\r\n5. edit nuxt.config.ts\r\n **nuxt.config.ts**\r\n ```\r\n export default defineNuxtConfig({\r\n components: [\r\n { path: '~/components/layouts', prefix: 'Special' },\r\n '~/components'\r\n ]\r\n })\r\n ```\r\n\r\n\r\n6. create **header.vue** under components/layouts\r\n ```\r\n \u003Ctemplate>\r\n \u003Cdiv>\r\n Header\r\n \u003C/div>\r\n \u003C/template>\r\n ```\r\n\r\n7. import header.vue in **app.vue**\r\n ```\r\n \u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CHeader />\r\n \u003CNuxtWelcome />\r\n \u003C/div>\r\n \u003C/template>\r\n \r\n \u003Cscript>\r\n import Header from '~/components/layouts/header.vue';\r\n \u003C/script>\r\n ```\r\n\r\n\r\n8. npm run dev\r\n\n\n### Describe the bug\n\n[Vue warn]: Failed to resolve component: Header\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2885,2888],{"name":2886,"color":2887},"3.x","29bc7f",{"name":2889,"color":2890},"pending triage","E99695",19310,"If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.","2023-02-27T12:15:17Z","https://github.com/nuxt/nuxt/issues/19310",0.657123,{"description":2897,"labels":2898,"number":2901,"owner":2857,"repository":2857,"state":2877,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Environment\n\nnuxt 3 rc12\r\nwin10\n\n### Reproduction\n\nIf i put project in one dir it work, if move to other not work. Always something not work.\n\n### Describe the bug\n\nruntime-core.esm-bundler.js:38 [Vue warn]: Failed to resolve component: nuxt-child\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\nruntime-core.esm-bundler.js:38 [Vue warn]: Hydration node mismatch:\r\n- Client vnode: nuxt-child \r\n- Server rendered DOM: \u003C!----> \r\n at \u003CQuality onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CAnonymous key=\"/quality\" routeProps= Object pageKey=\"/quality\" ... > \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 > \r\n at \u003CNuxtPage> \r\n at \u003CLayoutContent class=\"layoutContent py-0 bg-[#f8f8f8]\" > \r\n at \u003CLayout class=\"w-[100%] bg-[#f8f8f8]\" > \r\n at \u003CLayout class=\"flex h-[100%]\" has-sider=\"\" > \r\n at \u003CDefault > \r\n at \u003CAnonymous key=\"default\" name=\"default\" hasTransition=true > \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 \u003CConfigProvider inline-theme-disabled=\"\" theme-overrides= Object locale= Object ... > \r\n at \u003CMessageProvider> \r\n at \u003CDialogProvider> \r\n at \u003CApp key=1 > \r\n at \u003CNuxtRoot>\n```\n",[2899,2900],{"name":2886,"color":2887},{"name":2889,"color":2890},15309,"runtime-core.esm-bundler.js:38 [Vue warn]: Failed to resolve component: nuxt-child If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. ","2023-01-19T17:48:01Z","https://github.com/nuxt/nuxt/issues/15309",0.6580082,{"description":2907,"labels":2908,"number":2911,"owner":2857,"repository":2857,"state":2877,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.4.0`\r\n- Nitro Version: `2.3.3`\r\n- Package Manager: `npm@8.19.3`\r\n- Builder: `vite`\r\n- User Config: `app`, `runtimeConfig`, `css`, `modules`, `components`, `vite`, `vue`, `experimental`\r\n- Runtime Modules: `@nuxtjs/color-mode@3.2.0`, `@pinia/nuxt@0.4.8`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ruqb96?file=nuxt.config.ts\n\n### Describe the bug\n\nEnabling the Vue runtime compiler support in the `nuxt.config.ts`:\r\n\r\n```typescript\r\n experimental: {\r\n runtimeVueCompiler: true,\r\n externalVue: false,\r\n },\r\n```\r\n\r\nAlso adding `vue.compilerOptions.isCustomElement` config in the `nuxt.config.ts`:\r\n\r\n```typescript\r\n vue: {\r\n compilerOptions: {\r\n isCustomElement: (tag) =>\r\n isMathmlTag(tag) || tag.startsWith('bx-') || tag === 'custom-element',\r\n },\r\n },\r\n```\r\n\r\nWe have issues with the Vue runtime compiler support:\r\n\r\n- Failed to resolve component: custom-element\r\n- Failed to resolve component: math\r\n- Non-function value encountered for default slot. Prefer function slots for better performance\r\n- Component \u003CAnonymous> is missing template or render function.\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Failed to resolve component: custom-element 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: math 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: semantics 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: mrow 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: mi 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: annotation 6:28:56 AM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Non-function value encountered for default slot. Prefer function slots for better performance. 6:28:56 AM\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function. 6:28:56 AM\r\n[Vue warn]: Non-function value encountered for default slot. Prefer function slots for better performance. 6:28:56 AM\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function. 6:28:56 AM\r\n```\n```\n",[2909,2910],{"name":2886,"color":2887},{"name":2889,"color":2890},20228,"Issues with the Vue runtime compiler support","2023-04-12T13:58:48Z","https://github.com/nuxt/nuxt/issues/20228",0.6599675,{"description":2917,"labels":2918,"number":2921,"owner":2857,"repository":2857,"state":2877,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.0\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### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-4byrfr?file=modules%2Fcode-block.ts,app.vue\r\n\r\n### Describe the bug\r\n\r\nI have installed a vue component from NPM鈥痑nd created a nuxt module for it:\r\n\r\n```javascript\r\nimport { defineNuxtModule, addComponent } from '@nuxt/kit'\r\n\r\nexport default defineNuxtModule({\r\n setup() {\r\n addComponent({\r\n name: 'VCodeBlock',\r\n export: 'VCodeBlock',\r\n filePath: '@wdns/vue-code-block',\r\n mode: \"client\",\r\n })\r\n },\r\n})\r\n```\r\n\r\nHowever, despite `mode: \"client\"` whenever I put it in a nuxt page, layout or component I still get an ssr related issue\r\n\r\n```\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\nI also have the same error if I just import the component without using nuxt modules \r\nIf I completely disable SSR, it works fine. \r\n\r\nIf I鈥痳emove mode client, it's worse : it says window is undefined\r\n\r\nI would assume the problem is that the module is client side... but the component 鈥痷se it in isn't, therefore it's rendered before it should. \r\n\r\nIt does feel like a bug however because you'd assume mode client would work. What does `mode:client` do exactly ? \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\n",[2919,2920],{"name":2886,"color":2887},{"name":2889,"color":2890},24478,"node_modules component in nuxt modules : I still get SSR related errors despite `mode:client`","2023-11-28T23:34:19Z","https://github.com/nuxt/nuxt/issues/24478",0.66075397,{"labels":2927,"number":2930,"owner":2857,"repository":2857,"state":2877,"title":2931,"updated_at":2932,"url":2933,"score":2934},[2928,2929],{"name":2886,"color":2887},{"name":2889,"color":2890},14949,"Failed to resolve component in pages ","2023-01-19T17:42:57Z","https://github.com/nuxt/nuxt/issues/14949",0.6618735,{"description":2936,"labels":2937,"number":2945,"owner":2857,"repository":2857,"state":2877,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the feature\n\nthere is currently no way to configure `@vitejs/plugin-vue-jsx` via nuxt's config. see this line from `@nuxt/vite-builder` https://github.com/nuxt/nuxt/blob/523b495e1d808c3a1e57e190d73f460ddf3b3d8b/packages/vite/src/client.ts#LL63C23-L63C23\r\n\r\nmy use case is that i need to pass an `isCustomElement` function to the vue jsx plugin. the jsx plugin needs its own `isCustomElement` function (as well as the usual one you'd pass to the more common vue plugin). without this, i get \"Failed to resolve component\" warnings logged in the console.\r\n\r\nthere are two possible approaches to solving this that i see\r\n\r\n1. internally pass the same `isCustomElement` function to both vue and jsx plugins. i can't imagine why you'd ever need them to differ, and this means things would \"just work\" if you configure it once. however i understand this is a little magical, and may not be paletable to you\r\n2. a simpler option is to add a new config section specifically for the jsx plugin. this could be top-level alongside `vue` like `vueJsx`, or a child key of vue like `vue.jsx`, or whatever makes sense\r\n\r\ni am more than happy to work on a PR immediately for this following agreement from maintainers.\r\n\r\nthanks!\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [X] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2938,2939,2942],{"name":2886,"color":2887},{"name":2940,"color":2941},"vite","3574D1",{"name":2943,"color":2944},"馃嵃 p2-nice-to-have","0E8A16",19024,"add support for configuring @vitejs/plugin-vue-jsx's isCustomElement option","2023-02-16T12:45:10Z","https://github.com/nuxt/nuxt/issues/19024",0.66641814,{"description":2951,"labels":2952,"number":2957,"owner":2857,"repository":2857,"state":2877,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@4.0.1\r\n- Builder: -\r\n- User Config: devtools, app, modules, plausible, device, tailwindcss, vite, vue, imports, ssr, spaLoadingTemplate, piniaPersistedstate, runtimeConfig\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.10.3, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/device@3.1.1, @nuxtjs/plausible@0.2.4, @nuxtjs/algolia@1.10.1, @pinia-orm/nuxt@1.7.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/lukso-network/wallet.universalprofile.cloud\n\n### Describe the bug\n\nAfter upgrading from `nuxt@^3.6.5` to `nuxt@^3.9.0` I've started to see a lot of warnings regarding component resolving:\r\n\r\n```\r\nFailed to resolve component: lukso-sanitize\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```\r\n\r\nApp uses web components that's why in my `nuxt.config.ts` I have this entry which worked before upgrade:\r\n\r\n```\r\nvue: {\r\n compilerOptions: {\r\n isCustomElement: (tag: string) => {\r\n return tag.startsWith('lukso-')\r\n },\r\n },\r\n },\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2953,2954,2955],{"name":2886,"color":2887},{"name":2889,"color":2890},{"name":2956,"color":2875},"needs reproduction",25040,"Failed to resolve web component warning","2024-01-09T08:41:50Z","https://github.com/nuxt/nuxt/issues/25040",0.666544,{"description":2963,"labels":2964,"number":2969,"owner":2857,"repository":2857,"state":2877,"title":2970,"updated_at":2971,"url":2972,"score":2973},"Webpack externalizes dependencies like `@vueuse/head` in development mode. Since they are scopped to `node_modules/@nuxt/app/node_modules`, cannot be resolved. This also gives potential of duplicate versions being resolved. We can either transform app deps (reduces perf) or fully resolve webpack externals (reduces esm compatibility)",[2965,2966],{"name":2886,"color":2887},{"name":2967,"color":2968},"webpack","650C6F",11064,"@nuxt/app externals (@vueuse/head error)","2023-01-19T14:44:00Z","https://github.com/nuxt/nuxt/issues/11064",0.67036843,["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fETYuCYxbXLcWLFq51LOZXTg4TVaesemo9c2eBYc6KN4":-1},"/nuxt/nuxt/28060"]