\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_",[2054,2055],{"name":2028,"color":2029},{"name":1985,"color":2017},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.65672356,{"description":2062,"labels":2063,"number":2066,"owner":1988,"repository":2008,"state":2019,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v23.1.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\nhttps://github.com/brycesteve/nuxtUi500Repro\n\n### Description\n\nWhen using Nuxt UI from a layer, wrapping in `UApp` causes the following error:\n\n```\n500\nnull is not an object (evaluating 'currentRenderingInstance.ce')\n\nat renderComponentRoot (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3708:44)\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:465:65)\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:417:36)\nat ssrRenderComponent (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:57:32)\nat _sfc_ssrRender (:52:49)\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:460:20)\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:417:36)\nat ssrRenderComponent (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:57:32)\nat _sfc_ssrRender (:46:49)\n```\n\nRemoving `UApp` stops the error from happening. `UApp` also works correctly when not in a layer.\n\nIn the reproduction, Nuxt UI is added to the layer in `~/layers/ui`.\n\nRunning `bun --bun run dev` in the project root causes the error. Switching to `~/layers/ui` and running `bun --bun run dev` doesn't have the same error (`App.vue` in `~/layers/ui/.playground` is the same as the root `App.vue`). So, the issue is something to do with Nuxt UI being extended from a layer. The other components I've tried seem to work ok.\n\nI have read in a few places that this might be something to do with multiple Vue instances being created. But if it is, I can't seem to find a config that allows it to work.\n\nShould Nuxt UI work from a layer, or is it not compatible this way? If it should, is there something I'm doing wrong, or does anyone have a fix to make this work?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2064,2065],{"name":1999,"color":2000},{"name":2002,"color":2003},2622,"Nuxt UI in layer causes 500 error when wrapping in UApp","2024-12-05T13:48:51Z","https://github.com/nuxt/ui/issues/2622",0.6600013,{"description":2072,"labels":2073,"number":1987,"owner":1988,"repository":2080,"state":2019,"title":2081,"updated_at":2082,"url":2083,"score":1994},"Duplicate the support offer as displayed on nuxt.com landing page (see pic below) on nuxtjs.org \n\n\nand update NEN description with \"A network of experienced freelancers, officially certified by Nuxtlabs' lead engineers and all contributors to Nuxt OS projects\" + put capital letter on \"Nuxt Experts Network\"",[2074,2077],{"name":2075,"color":2076},"enhancement","1ad6ff",{"name":2078,"color":2079},"marketing","f5c828","nuxt.com","[Landing Nuxtjs.org] include support offers on nuxtjs.org landing page","2023-10-03T13:46:53Z","https://github.com/nuxt/nuxt.com/issues/1115",{"description":2085,"labels":2086,"number":2089,"owner":1988,"repository":2008,"state":2019,"title":2090,"updated_at":2091,"url":2092,"score":2093},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@9.6.7\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, @nuxt/eslint@0.7.2, @nuxtjs/i18n@9.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\nNone\n\n### Description\n\nThank you very much for providing such a great component library. I'm trying to use it in my personal project.\n\nThe following is the relevant code:\n```ts\nconst columns = computed(() => defaultColumns.filter(column => selectedColumns.value.includes(column.accessorKey)))\n```\n```vue\n\u003CUTable\n :columns=\"columns\"\n :data=\"data\"\n/>\n```\n\n---\nI checked the latest documentation, and the examples of UTable regarding column display control seem to have no effect, such as: https://ui3.nuxt.dev/components/table#with-column-visibility.\n\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2087,2088],{"name":1999,"color":2000},{"name":2002,"color":2003},2874,"The update of the columns property will not trigger an update of the UTable component","2025-01-25T13:12:40Z","https://github.com/nuxt/ui/issues/2874",0.6609228,{"description":2095,"labels":2096,"number":2101,"owner":1988,"repository":1988,"state":2019,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### 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_",[2097,2098,2099],{"name":2028,"color":2029},{"name":1985,"color":2017},{"name":2100,"color":2045},"needs reproduction",25040,"Failed to resolve web component warning","2024-01-09T08:41:50Z","https://github.com/nuxt/nuxt/issues/25040",0.6670915,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"JpRmX4w6vVtAo4yXqpMaGt_7cld5D-E3xOuR1nyE3bk":-1},"/nuxt/nuxt.com/1653"]