\r\n \u003C/NuxtLayout>\r\n \u003C!-- universal components -->\r\n \u003CMenuDialog />\r\n \u003CLanguageDialog />\r\n \u003CColorModeDialog />\r\n \u003CBackdrop />\r\n \u003C!-- etc -->\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\nOr you could just move those components to a directory called `~/components/universal` (for example) and Nuxt would take care of injecting them automatically.\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] 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).",[2886,2887],{"name":2868,"color":2869},{"name":2888,"color":2889},"discussion","538de2",19492,"Components automatically injected into the root element","2024-06-30T11:09:20Z","https://github.com/nuxt/nuxt/issues/19492",0.68721396,{"description":2896,"labels":2897,"number":2902,"owner":2877,"repository":2877,"state":2903,"title":2904,"updated_at":2905,"url":2906,"score":2907},"- [x] Initial working version from [@nuxt/components](https://github.com/nuxt/components)\r\n- [x] `.dts` generation\r\n- [x] Decide about prefix\r\n- [x] Implement loader strategy (vite and webpack5) \r\n- [ ] Integrate with devtools\r\n\r\n### Discussion: Should we even have it with nuxt3?\r\n\r\nRelated tweet (https://twitter.com/youyuxi/status/1404795327144763398). I think that makes sense in many ways that auto-import is not that needed with new `\u003Cscript setup>` syntax and better VSCode integrations. But there are still some cases most notable, CMS/Content integrations that implicitly need global components. And also this gives possibility with nuxt devtools component playground\r\n\r\n### Discussion: Where to implement?\r\n\r\nIn `framework/packages/components` as a fork of `nuxt/components` and add by default in `nuxt3`\r\n\r\n### Discussion: Prefixing\r\n\r\nShould we use (by default) one level prefix `components/utils/bar/baz` => `BarBaz` or full prefix => `UtilsBarBaz` or not at all (`Baz`) by default (suggested by @Atinux). Second is much more future proof but less convenient for structuring components dir based on purpose (and atomic designs)",[2898,2899],{"name":2888,"color":2889},{"name":2900,"color":2901},"3.x","29bc7f",11026,"closed","Components Discovery","2023-01-19T14:46:30Z","https://github.com/nuxt/nuxt/issues/11026",0.6533132,{"description":2909,"labels":2910,"number":2917,"owner":2877,"repository":2877,"state":2903,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Reproduction link\n\n[https://github.com/meta7x/nuxt-global-components-bug](https://github.com/meta7x/nuxt-global-components-bug)\n\n### Steps to reproduce\n\n- Download reproduction repository\n- Run '$npm install' in the root directory\n- [optional] run $npm run dev: the page renders the expected result with the global component showing under the Nuxt logo.\n- '$cd functions' and run '$npm install' to install Nuxt inside the functions folder\n- '$cd .. $npm run dev': the page renders, but there is no global component and there is an error message in the console\n- run '$cd functions $npm remove nuxt' to get everything working again\n\n### What is expected ?\n\nNuxt is still expected to render the page the same way as before.\n\n### What is actually happening?\n\nInstead it registers the component correctly, which can be seen in the console logs, but at the same time it throws an error \"unknown custom element\". Local components still work fine, as can be seen with the Nuxt logo.\n\nPossibly global mixins don't work either, but I haven't tested that in an isolated environment, also because I'm not quite sure what the correct way to global mixins is in Nuxt.\n\n### Additional comments?\n\nThe reason I want to build to build into the functions directory is because I want to SSR with Firebase Functions, which needs to import the Nuxt-class in order to create a Nuxt-instance. Have a look at functions/index.js to see what exactly needs to happen for the app to SSR.\nI've been tracking down this error for some time now and it really seems to all come down to whether the second Nuxt-module is inside the functions folder.\nBuilding to any other folder works fine and the public path also doesn't seem to have a big influence.\n\nFiles of importance:\n- components/GlobalComponent.vue: an example component that I would like to use globally\n- plugins/global.js: for registering the global component\n- pages/index.vue: the global component is used there alongside a local component\n- functions/index.js: the code that is supposed to SSR the app\n- nuxt.config.js - obviously\n\nIf there's a workaround anyone can come up with, I'd be glad to hack my way around this problem as well. Just importing every component in every other component isn't a great solution though, especially since I have a hunch that my global mixin isn't working for the same reason.\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c7179\">#c7179\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2911,2914],{"name":2912,"color":2913},"pending triage","E99695",{"name":2915,"color":2916},"2.x","d4c5f9",3397,"Nuxt fails to load global components when built to functions directory for Firebase Functions SSR","2023-01-22T15:30:04Z","https://github.com/nuxt/nuxt/issues/3397",0.67304164,{"labels":2923,"number":2926,"owner":2877,"repository":2877,"state":2903,"title":2927,"updated_at":2928,"url":2929,"score":2930},[2924,2925],{"name":2868,"color":2869},{"name":2900,"color":2901},12790,"Support `global: false` for components","2023-01-19T16:35:12Z","https://github.com/nuxt/nuxt/issues/12790",0.6747019,{"labels":2932,"number":2935,"owner":2877,"repository":2877,"state":2903,"title":2936,"updated_at":2937,"url":2938,"score":2939},[2933,2934],{"name":2868,"color":2869},{"name":2900,"color":2901},12962,"Type Support for Global Components (e.g. `\u003Cnuxt-link>`)","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12962",0.67662024,{"description":2941,"labels":2942,"number":2945,"owner":2877,"repository":2877,"state":2903,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Version\n\n[v2.0.0](https://github.com/nuxt.js/releases/tag/v2.0.0)\n\n### Reproduction link\n\n[https://codesandbox.io/s/o96v4m0k76](https://codesandbox.io/s/o96v4m0k76)\n\n### Steps to reproduce\n\n1. Add `plugins/global.js` and import `Vue` and a component.\n2. Register the component with `Vue.component('my-comp', Component)`\n3. Add `plugins: [ '@/plugins/global.js' ]`in `nuxt.config.js`\n4. Use `\u003Cmy-comp>\u003C/my-comp>`\n\n### What is expected ?\n\nComponent should be registered with Vue and can be used globally.\n\n### What is actually happening?\n\nErrors shown.\n\n\n```\n- [Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content.\n- [Vue warn]: Unknown custom element: \u003Cmy-comp> - did you register the component correctly?\n```\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7863\">#c7863\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2943,2944],{"name":2912,"color":2913},{"name":2915,"color":2916},4006,"Global components registered with plugins is not loaded on client side","2023-01-22T15:30:07Z","https://github.com/nuxt/nuxt/issues/4006",0.6796759,{"description":2951,"labels":2952,"number":2955,"owner":2877,"repository":2877,"state":2903,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Environment\r\n\r\nRootDir: /home/projects/github-zxwxk5-aqc6tg \r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: modules, components\r\n- Runtime Modules: @rah-emil/vite-plugin-vue-type-imports/nuxt@0.2.5\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n\r\nHere is reproduction, there are two components. \r\n`components/DemoWork.vue` - it uses `MyInterface` imported from types and it works\r\n`components/globals/Demo.vue` - it uses `MyInterface` imported from types and it doest not work\r\n\r\none difference is the `components/globals/Demo` is attached by autoimport\r\n\r\nTo run project properly you have to comment nuxt.config.ts\r\n```js\r\n components: [{ path: '~/components/globals', global: true }, '~/components'],\r\n```\r\nhttps://stackblitz.com/edit/github-zxwxk5-aqc6tg?file=components/globals/Demo.vue\r\n\r\n### Describe the bug\r\n\r\nWe are using a plugin (https://github.com/rah-emil/vite-plugin-vue-type-imports/blob/main/src/core/index.ts) for Vite that allows us to import external types as component props interfaces. However, in version 3.4.3, we noticed that the plugin still works but global components attached by autoimport no longer work.\r\n\r\nCan we do something about this? Our library uses global components with imported types and now we have regression. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2953,2954],{"name":2900,"color":2901},{"name":2912,"color":2913},20720,"Global components attached by autoimports do not respect the Vite plugin (3.4.3)","2023-05-22T07:04:36Z","https://github.com/nuxt/nuxt/issues/20720",0.6798793,{"description":2961,"labels":2962,"number":2974,"owner":2877,"repository":2877,"state":2903,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.8.0\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@9.7.2\r\n- Builder: vite\r\n- User Config: ssr, srcDir, devtools, extends, vite, modules, graphql-client, app\r\n- Runtime Modules: vuetify-nuxt-module@0.5.7, nuxt-gtag@0.5.9, nuxt-graphql-client@0.2.30\r\n- Build Modules: -\n\n### Reproduction\n\nHave your main App with:\r\n```\r\nexport default defineNuxtConfig({\r\n extends: [\r\n './layers/my_awesome_layer',\r\n ],\r\n})\r\n```\r\n\r\nHave a simple page doing something like:\r\n```\r\n\u003Ctemplate>\r\n \u003CTheNavbar />\r\n\u003C/template>\r\n```\r\n\r\nWith the component TheNavbar being in your layer.\r\nIf I add\r\n```\r\n components: {\r\n dirs: [\r\n {\r\n path: '~/components/global',\r\n global: true,\r\n },\r\n '~/components',\r\n ],\r\n },\r\n```\r\n\r\nIn the config of my layer so I can use `\u003Ccomponent :is=\"resolveComponent('TheNavbar')\" />`\r\n\r\n\n\n### Describe the bug\n\nThe overall problem is that I have an UI-Kit layer with a lot of components.\r\nAnd in my pages I must call an external API with fetch to retrieve an array of components.\r\nThen I have to use the dynamic \u003Ccomponent :is /> but when I try to globally register my layer components it does not work at all and even when it's not dynamic those layer components are unkwown.\r\n\r\nSo is it a bug?\r\n\r\nWhat would be the best practice to have dynamic component with name fetched from an external API on a page and with all of them registered in a layer?\r\n\r\nThank you all!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2963,2964,2965,2968,2971],{"name":2900,"color":2901},{"name":2912,"color":2913},{"name":2966,"color":2967},"needs reproduction","FBCA04",{"name":2969,"color":2970},"layers","006B75",{"name":2972,"color":2973},"closed-by-bot","ededed",22704,"Marking Layer Components Global = Failed To Resolve","2023-09-07T01:47:44Z","https://github.com/nuxt/nuxt/issues/22704",0.6799106,{"labels":2980,"number":2988,"owner":2877,"repository":2877,"state":2903,"title":2989,"updated_at":2990,"url":2991,"score":2992},[2981,2982,2985],{"name":2900,"color":2901},{"name":2983,"color":2984},"bug","d73a4a",{"name":2986,"color":2987},"❗ p4-important","D93F0B",13429,"Auto import of components broken","2023-01-19T16:55:49Z","https://github.com/nuxt/nuxt/issues/13429",0.68235064,["Reactive",2994],{},["Set"],["ShallowReactive",2997],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fI7o2uC8Bg4DQp7vGTsHbS_Fku_m0pvDezdRrr36HQOU":-1},"/nuxt/nuxt/14051"]