\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_",[3194,3195,3198],{"name":3140,"color":3141},{"name":3196,"color":3197},"pages","00DFB5",{"name":3183,"color":3184},28732,"NuxtLink with custom directive is throwing console warning","2024-08-28T11:32:00Z","https://github.com/nuxt/nuxt/issues/28732",0.6688005,{"labels":3205,"number":3212,"owner":3149,"repository":3149,"state":3186,"title":3213,"updated_at":3214,"url":3215,"score":3216},[3206,3209],{"name":3207,"color":3208},"pending triage","E99695",{"name":3210,"color":3211},"2.x","d4c5f9",10593,"@click listener on \u003Cnuxt-link> or \u003Crouter-link> no longer works inside page components on Vue 2.7","2023-02-08T19:37:35Z","https://github.com/nuxt/nuxt/issues/10593",0.67959553,{"description":3218,"labels":3219,"number":3221,"owner":3149,"repository":3149,"state":3186,"title":3222,"updated_at":3223,"url":3224,"score":3225},"I need to add a listening keyboard event to the page, but now I'm using nuxt to add the listener failure.\r\n\r\n`\r\ncreated(){\r\n //注册全局变量\r\n\r\n if(process.browser){\r\n const _this = this;\r\n _this.hotelMarquee = this.hotel[this.language_code].length>18;\r\n document.onkeydown = function(e) {\r\n _this.changeLanguage(e.which)\r\n };\r\n }\r\n },\r\n}\r\n`\r\nThe results of the operation are wrongly reported as follows:\r\n\r\n`\r\n[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside \u003Cp>, or missing \u003Ctbody>. Bailing hydration and performing full client-side render.\r\n`\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2680\">#c2680\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3220],{"name":3210,"color":3211},3096,"How do I add a listener event on the server side?","2023-01-18T16:09:58Z","https://github.com/nuxt/nuxt/issues/3096",0.68925047,{"description":3227,"labels":3228,"number":3231,"owner":3149,"repository":3149,"state":3186,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Environment\r\n\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.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, vite\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-s3ebia?file=app.vue,components%2FFullscreenBackground.vue\r\n\r\n### Describe the bug\r\n\r\nI was making a background for a modal component when I noticed a strange behaviour with the `\u003CTransition />` component, specifically when the `appear` prop is set.\r\n\r\nIt seems that the click event listener on an element inside `\u003CTransition appear>` isn't being properly handled.\r\nSteps to reproduce:\r\n1. open the reproduction\r\n2. click on the semi-transparent fullscreen div\r\n3. *nothing happens* even though it should have set its visibility to `false`\r\n\r\n1. remove `appear` from the `\u003CTransition>` component in `FullscreenBackground.vue`\r\n2. repeat the same steps & now the click is properly handled\r\n\r\n### Additional context\r\n\r\nI've tried and I couldn't reproduce the same issue in Vue, so I assume it could be a bug in Nuxt.\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3229,3230],{"name":3179,"color":3180},{"name":3207,"color":3208},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.6934829,{"description":3237,"labels":3238,"number":3248,"owner":3149,"repository":3150,"state":3186,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Environment\n\nNuxt project info: (copied to clipboard) nuxi 10:36:44\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, experimental, nitro, sourcemap, ssr, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.1, @nuxtjs/mdc@0.15.0, @vueuse/nuxt@13.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n\nInput Menu Send an event when using @Change\n\n\n\nBut it is scheduled to send a value and this generates the error in console\n\n\n\n\n\n### Description\n\nhttps://github.com/user-attachments/assets/3fdd5798-3f77-45e0-a86b-18a2195219f2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3239,3240,3243,3244,3245],{"name":3140,"color":3141},{"name":3241,"color":3242},"needs reproduction","CB47CF",{"name":3143,"color":3144},{"name":3146,"color":3147},{"name":3246,"color":3247},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.6954109,{"description":3254,"labels":3255,"number":3257,"owner":3149,"repository":3149,"state":3186,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.8.1\r\n- Builder: -\r\n- User Config: srcDir, components, devtools, modules, vite, hooks, app, runtimeConfig\r\n- Runtime Modules: @vueuse/nuxt@10.11.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-vxspid?file=src%2Fplugins%2FclickOutside.ts\n\n### Describe the bug\n\nHello, not sure if you can help with this. I'm trying to implement a basic click outside functionality in a nuxt app.\r\nI'm trying to use @vueuse/components and I import @vueuse/nuxt in modules in nuxt config.\r\nmodules: [\r\n '@vueuse/nuxt',\r\n ],\r\n Then I create a plugin with this\r\n \r\n import { vOnClickOutside } from '@vueuse/components'\r\n\r\nexport default defineNuxtPlugin((nuxtApp) => {\r\n nuxtApp.vueApp.directive('clickOutside', vOnClickOutside)\r\n})\r\n\r\nHowever, I keep receiving this message after trying to use the dom element \u003COnClickOutside> in the HTML of the page :\r\n\r\n[Vue warn]: Failed to resolve component: OnClickOutside \r\nIf this is a native custom element, make sure to exclude it from \r\ncomponent resolution via compilerOptions.isCustomElement.\r\n\r\nIf I try to use the v-on-click-outside directive in the HTML I receive the following error : \r\n\r\n[Vue warn]: Failed to resolve directive: on-click-outside\r\n\r\nI don't know which would be a correct solution for this.\r\n\r\nThank you in advance for your help\r\n\r\nCarlota\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3256],{"name":3207,"color":3208},28060,"@vueuse/nuxt + @vueuse/components => vOnClickOutside","2024-07-05T22:04:25Z","https://github.com/nuxt/nuxt/issues/28060",0.6980425,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fP2KGr5ggp5DGObhfzR_JusZYEzWwBmw3c-r_4UGq5Ac":-1},"/nuxt/ui/4268"]