\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_",[2000,2001,2002,2005,2008],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2003,"color":2004},"needs reproduction","FBCA04",{"name":2006,"color":2007},"layers","006B75",{"name":2009,"color":2010},"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.6504264,{"labels":2017,"number":2022,"owner":1991,"repository":1991,"state":1992,"title":2023,"updated_at":2024,"url":2025,"score":2026},[2018,2021],{"name":2019,"color":2020},"enhancement","8DEF37",{"name":1985,"color":1986},12962,"Type Support for Global Components (e.g. `\u003Cnuxt-link>`)","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12962",0.6570111,{"description":2028,"labels":2029,"number":2036,"owner":1991,"repository":1991,"state":1992,"title":2037,"updated_at":2038,"url":2039,"score":2040},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-jzao4p?file=modules%2Fsome-module%2Findex.ts\n\n### Describe the bug\n\nThe reproduction contains a nuxt module that adds 2 components. `DComp` that is exported as `default` and `NComp` that is exported as named `NComp`. When registering these components as client-only via `addComponent` the `DComp` works correctry. However `NComp` is apparently not found.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Invalid vnode type when creating vnode: undefined.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\n```\n",[2030,2031,2034],{"name":1985,"color":1986},{"name":2032,"color":2033},"bug","d73a4a",{"name":2035,"color":2004},"🔨 p3-minor",25281,"Cannot register named exported components as client-only","2024-01-20T20:43:13Z","https://github.com/nuxt/nuxt/issues/25281",0.6591574,{"description":2042,"labels":2043,"number":2047,"owner":1991,"repository":1991,"state":1992,"title":2048,"updated_at":2049,"url":2050,"score":2051},"### Environment\n\n➜ npx nuxi info\r\nNuxi 3.0.0-rc.9 11:55:40\r\nRootDir: /Users/angurias/Developer/helium/sp-product-frontend-2 11:55:42\r\nNuxt project info: 11:55:42\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0-rc.9`\r\n- Nitro Version: `0.5.1`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `typescript`, `srcDir`, `modules`, `css`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@5.3.3`\r\n- Build Modules: `-`\r\n------------------------------\r\n\n\n### Reproduction\n\n- Have lots of components\r\n- Try to import lots of components (not necessarily all of them) via code in a ts file E.G:\r\n```\r\nimport {\r\n IconBasicArrowBottomSmall,\r\n IconBasicArrowDown,\r\n IconBasicArrowLeftSmall,\r\n IconBasicArrowLeft,\r\n IconBasicArrowRightSmall,\r\n IconBasicArrowRight,\r\n IconBasicArrowTopSmall,\r\n IconBasicArrowTop,\r\n IconBasicCalculator,\r\n IconBasicCalendar,\r\n IconBasicCheck,\r\n IconBasicDashboard,\r\n IconBasicEdit,\r\n IconBasicEnter,\r\n IconBasicExit,\r\n IconBasicHelp,\r\n IconBasicHide,\r\n IconBasicShow,\r\n IconBasicTrash,\r\n IconBasicUpload,\r\n IconBasicAlertCircle,\r\n IconBasicCarretDown,\r\n IconBasicCarretLeft,\r\n IconBasicCarretRight,\r\n IconBasicCarretUp,\r\n IconBasicCheckCircle,\r\n IconBasicComment,\r\n IconBasicCreditCard,\r\n IconBasicDots,\r\n IconBasicErrorCircle,\r\n IconBasicHome,\r\n IconBasicInfoCircle,\r\n IconBasicLockClose,\r\n IconBasicLockOpen,\r\n IconBasicMoney,\r\n IconBasicPlusCircleLight,\r\n IconBasicPlus,\r\n IconBasicSlider,\r\n IconBasicTimesCircleLight,\r\n IconBasicTimesCircle,\r\n IconBasicTimes,\r\n IconCalendarCopy,\r\n IconCalendarModFreeze,\r\n IconCalendarModMarkup,\r\n IconCalendarModMax,\r\n IconCalendarModMin,\r\n IconCalendarEuroSmall,\r\n IconCalendarMinusSmall,\r\n IconCalendarPercentSmall,\r\n IconCalendarPlusSmall,\r\n IconCalendarUserAlt,\r\n IconCalendarUser,\r\n IconDashboardBarGraph,\r\n IconDashboardLineGraph,\r\n IconLangDe,\r\n IconLangEn,\r\n IconLangIt,\r\n} from '~~/.nuxt/components'\r\n```\r\n\r\n(In my specific case I'm making a `Map` containing them)\n\n### Describe the bug\n\nMultiple errors can be triggered:\r\n 1. Sometimes it will compile, but an error stating the import is not an html will be triggered\r\n 2. Sometimes it will fail before compile time, stating that one (or multiple) of the components needs to be initialized\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2044,2045,2046],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2003,"color":2004},14859,"Autoimported components (~~/.nuxt/components) are not reliable code-wise","2023-01-19T17:41:35Z","https://github.com/nuxt/nuxt/issues/14859",0.66430473,{"description":2053,"labels":2054,"number":2058,"owner":1991,"repository":1991,"state":1992,"title":2059,"updated_at":2060,"url":2061,"score":2062},"Hi there!\r\n\r\nI just experiencing an issue that `global components` that defined in `plugins/` directory doesn't seems to work on production build.\r\n\r\n\r\n\r\n> left : build & run on production mode\r\n> right : run development server\r\n\r\nI've assure that this issue only happened on client side rendering because i've check the server side rendering seems to work just fine.\r\n\r\n\r\n\r\nThe global component `\u003Capp-main />` is registered on `/plugins/global-components.js` file here\r\n\r\n\r\n\r\nand here my `nuxt.config.js` file\r\n\r\n```js\r\n'use strict'\r\n\r\nconst { resolve } = require('path')\r\nconst Env = use('Env')\r\n\r\nmodule.exports = {\r\n build: {\r\n publicPath: Env.get('CDN_URL', '/'),\r\n\r\n analyze: {\r\n analyzerMode: 'static',\r\n generateStatsFile: true,\r\n statsFilename: 'webpack-stats.json'\r\n },\r\n\r\n extractCSS: true,\r\n\r\n postcss: {\r\n plugins: {\r\n 'postcss-custom-properties': false\r\n }\r\n }\r\n },\r\n\r\n css: [\r\n '~assets/scss/main.scss'\r\n ],\r\n\r\n head: {\r\n htmlAttrs: {},\r\n\r\n meta: [\r\n {\r\n charset: 'utf-8'\r\n },\r\n {\r\n name: 'viewport',\r\n content: 'width=device-width,initial-scale=1'\r\n },\r\n {\r\n 'http-equiv': 'x-ua-compatible',\r\n content: 'ie=edge,chrome=1'\r\n },\r\n {\r\n name: 'theme-color',\r\n content: '#ffffff'\r\n }\r\n ],\r\n\r\n link: [\r\n {\r\n rel: 'shortcut icon',\r\n type: 'image/x-icon',\r\n href: '/favicon.ico'\r\n },\r\n {\r\n rel: 'apple-touch-icon',\r\n size: '192x192',\r\n href: '/mobile-icon.png'\r\n },\r\n {\r\n rel: 'icon',\r\n type: 'image/png',\r\n size: '192x192',\r\n href: '/mobile-icon.png'\r\n },\r\n {\r\n rel: 'icon',\r\n type: 'image/png',\r\n size: '32x32',\r\n href: '/favicon.png'\r\n },\r\n {\r\n rel: 'stylesheet',\r\n href: 'https://fonts.googleapis.com/css?family=Montserrat:300,400,600'\r\n }\r\n ],\r\n\r\n noscript: [{\r\n innerHtml: `\r\n \u003Ch1>Javascript Disabled\u003C/h1>\r\n \u003Cp>It appears that you do not have Javascript enabled. This application relies on Javascript for most of our features.\u003Cp>\r\n \u003Cp>Please enable Javascript and \u003Ca href=\".\">reload\u003C/a> in order to use this site.\u003C/p>\r\n `}]\r\n },\r\n\r\n loading: {\r\n color: '#589d8d'\r\n },\r\n\r\n plugins: [\r\n '~/plugins/global-components.js'\r\n ],\r\n\r\n router: {\r\n base: '/',\r\n linkActiveClass: '',\r\n linkExactActiveClass: 'is-active',\r\n\r\n scrollBehaviour: () => ({\r\n x: 0,\r\n y: 0\r\n }),\r\n\r\n extendRoutes: (routes) => {\r\n routes.forEach((route) => {\r\n route.meta = {\r\n title: route.name\r\n }\r\n })\r\n }\r\n },\r\n\r\n buildDir: resolve(__dirname, '..', 'public'),\r\n srcDir: resolve(__dirname, '..', 'resources')\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/c2492\">#c2492\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2055],{"name":2056,"color":2057},"2.x","d4c5f9",2868,"global components non rendered properly on production build?","2023-01-18T16:09:43Z","https://github.com/nuxt/nuxt/issues/2868",0.66781664,{"description":2064,"labels":2065,"number":2068,"owner":1991,"repository":1991,"state":1992,"title":2069,"updated_at":2070,"url":2071,"score":2072},"### 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>",[2066,2067],{"name":1988,"color":1989},{"name":2056,"color":2057},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.66845214,{"description":2074,"labels":2075,"number":2082,"owner":1991,"repository":1991,"state":1992,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.17.1`\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.6.7`\r\n- Builder: `-`\r\n- User Config: `devtools`, `imports`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n1. go to https://github.com/DawidKopys/nuxt-props-with-global-types/ and clone this repo\r\n2. `npm i`\r\n3. `npm run type-check`\r\n\r\n**Expected result**: we get typescript error in App.vue in place of using CompUsingGlobalType1 as we are passing number instead of string to its prop foo.bar.\r\n\r\n**Actual result**: there is no typescript error in above place.\r\n\r\n### Describe the bug\r\n\r\nFirst of all, let me thank all of the people involved in developing Nuxt. You are doing a great job creating this awesome piece of software!\r\n\r\nNow back to the issue:\r\nIt seems that types auto imported by Nuxt can't be used for defining components' props (without importing them explicitly, for example from `#imports`). In fact it's even worse - they can be used, we don't get any ts errors, it just doesn't seem to work. It looks that it fails silently.\r\n\r\nWhat is more, it also presents that globally available types can be used for defining props, just not if they are made available globally the way it is currently done in Nuxt.\r\n\r\nTo keep it brief:\r\n- global types added to the global scope in the way Nuxt does that don't work when used for defining vue components' props. It seems that Nuxt is generating something alike below snippet inside `.nuxt/types/imports.d.ts`\r\n```typescript\r\ndeclare global {\r\n // @ts-ignore\r\n export type { GlobalExternalType1 } from './GlobalExternalType1'\r\n}\r\n\r\n```\r\n- it seems that it could work, if Nuxt was generating something like below instead:\r\n```typescript\r\ndeclare global {\r\n interface GlobalExternalType2 {\r\n bar: string\r\n }\r\n}\r\n```\r\nIt would possibly require to copy over entire types' declarations in order to do that. But maybe it wouldn't be a problem since TypeScript is a structural type system and when comparing types, TypeScript only takes into account the members on the type.\r\n\r\n\r\n### Additional context\r\n\r\nFor additional info see https://github.com/DawidKopys/vue-props-with-global-types#readme as well. The same issue but with plain vue project, without Nuxt.\r\n\r\n### Logs\r\n\r\n_No response_",[2076,2077,2078,2079],{"name":2019,"color":2020},{"name":1985,"color":1986},{"name":2032,"color":2033},{"name":2080,"color":2081},"🍰 p2-nice-to-have","0E8A16",24412,"Types auto imported by Nuxt can't be used for defining components' props","2024-03-28T19:37:47Z","https://github.com/nuxt/nuxt/issues/24412",0.6737347,{"description":2088,"labels":2089,"number":2101,"owner":1991,"repository":1991,"state":1992,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### Environment\n\nStackblitz\r\n\r\n````\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: -\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: extends\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n````\n\n### Reproduction\n\nhttps://stackblitz.com/github/martinszeltins/found-nuxt-components-issue?file=app.vue\n\n### Describe the bug\n\nWhen I add this module to my modules array in nuxt.config.ts then I lose all typings for my components _(for both local and 3rd party components)._ It shows that components have type of `unknown`. Before I add this module, everything works.\r\n\r\n**nuxt.config.ts** 👇️\r\n```diff\r\nmodules: [\r\n+ '@nuxtjs/i18n', // This breaks all auto-import component typings (components not recognized anymore)\r\n '@vueuse/nuxt',\r\n 'nuxt-primevue'\r\n],\r\n```\r\n\r\nIf I remove it from my modules array then everything works again.\r\n\r\n**Screenshot before adding the module (everything works):** 👍️ 👇️\r\n\r\n\r\n\r\n**Screenshot after adding the module (type unknown):** ❌ 👇️\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2090,2093,2094,2097,2098],{"name":2091,"color":2092},"types","2875C3",{"name":1985,"color":1986},{"name":2095,"color":2096},"workaround available","11376d",{"name":2032,"color":2033},{"name":2099,"color":2100},"upstream","E8A36D",26214,"Adding `@nuxtjs/i18n` to Nuxt breaks component types (shows unknown)","2024-05-27T10:28:40Z","https://github.com/nuxt/nuxt/issues/26214",0.6747111,{"labels":2107,"number":2116,"owner":1991,"repository":1991,"state":1992,"title":2117,"updated_at":2118,"url":2119,"score":2120},[2108,2109,2110,2113],{"name":1985,"color":1986},{"name":2032,"color":2033},{"name":2111,"color":2112},"components","05B979",{"name":2114,"color":2115},"❗ p4-important","D93F0B",13538,"Autoimport components dir","2023-10-06T09:49:35Z","https://github.com/nuxt/nuxt/issues/13538",0.6762627,["Reactive",2122],{},["Set"],["ShallowReactive",2125],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"rIhWqRPsSqrlSmSNELlEEIJ7IJ6nPJ9GJNknlX-utbc":-1},"/nuxt/nuxt/26471"]