\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncomponents/content/Container.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nlayouts/full.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"custom-layout\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncontent/index.md:\r\n```markdown\r\n---\r\nlayout: 'full'\r\n---\r\n\r\n:component-with-icon\r\n\r\n::container\r\nSlot nr 1\r\n::::container\r\nSlot nr 2\r\n::::\r\n::\r\n```\r\n\r\nThis bug prevents the site from being used in development mode due to the infinity loop. The problem does not occur in the latest beta version of nuxt-icon, but in the original project I use nuxt-ui, which uses the old version \r\n",[],157,"Infinite WARN loop with slots and nuxt-content","2024-09-06T11:17:31Z","https://github.com/nuxt/icon/issues/157",0.7127564,{"description":2926,"labels":2927,"number":2936,"owner":2874,"repository":2874,"state":2912,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the feature\r\n\r\nMoving components registration in Vuetify Nuxt module from custom Vuetify Vite plugin to Nuxt component loader (`components:extend` hook) found missing auto importing directives here.\r\n\r\nThis is done in [Vuetify Vite plugin](https://github.com/vuetifyjs/vuetify-loader/blob/master/packages/vite-plugin/src/importPlugin.ts#L28-L49) via its shared package: check `getImports.ts` and `generateImports.ts` here https://github.com/vuetifyjs/vuetify-loader/tree/master/packages/shared/src/imports \r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2928,2930,2933],{"name":2894,"color":2929},"8DEF37",{"name":2931,"color":2932},"good first issue","fbca04",{"name":2934,"color":2935},"🍰 p2-nice-to-have","0E8A16",28954,"allow auto import vue directives","2025-01-17T00:15:26Z","https://github.com/nuxt/nuxt/issues/28954",0.7182471,{"description":2942,"labels":2943,"number":2948,"owner":2874,"repository":2875,"state":2912,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2944,2947],{"name":2945,"color":2946},"question","d876e3",{"name":2897,"color":2898},3525,"Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.72553384,{"labels":2954,"number":2961,"owner":2874,"repository":2874,"state":2912,"title":2962,"updated_at":2963,"url":2964,"score":2965},[2955,2958],{"name":2956,"color":2957},"pending triage","E99695",{"name":2959,"color":2960},"2.x","d4c5f9",10114,"Custom directives didn't recognized by Nuxt v3","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10114",0.7277111,{"description":2967,"labels":2968,"number":2970,"owner":2874,"repository":2874,"state":2912,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### 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_",[2969],{"name":2956,"color":2957},28060,"@vueuse/nuxt + @vueuse/components => vOnClickOutside","2024-07-05T22:04:25Z","https://github.com/nuxt/nuxt/issues/28060",0.72837484,{"description":2976,"labels":2977,"number":2980,"owner":2874,"repository":2911,"state":2912,"title":2981,"updated_at":2982,"url":2983,"score":2984},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2978],{"name":2868,"color":2979},"ff281a",496,"[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.7297474,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fU5nOO55rmlFxRGqDIp5g2fxJnnnvHhuhn287yRbschI":-1},"/nuxt/nuxt.com/1197"]