\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vSqMC30k7Rm\n\nBy the way, in non-multiple mode i cant remove value... https://skr.sh/vSqNhU5VYrM",[2030,2033],{"name":2031,"color":2032},"bug","d73a4a",{"name":2034,"color":2035},"v3","49DCB8","ui","UInputMenu not triggering when remove items in multiple mode","2025-01-25T13:12:42Z","https://github.com/nuxt/ui/issues/2743",{"description":2041,"labels":2042,"number":2045,"owner":1988,"repository":1988,"state":1989,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Versions\r\n\r\n- nuxt: v2.15.8\r\n- node: v16.5.0\r\n\r\n### Reproduction\r\n\r\nAfter upgrading to Nuxt v.2.15.8, I encountered an issue where Vue components inside a Nuxt Content file stopped working.\r\nHowever, this is only the case when statically generating the pages.\r\nThey work fine in dev mode.\r\n\r\nSee https://github.com/DerYeger/magdalena-jirku or https://github.com/DerYeger/jan-mueller for examples.\r\nSee https://github.com/DerYeger/jan-mueller/runs/3313688848 for the log of a failed build.\r\n\r\n### Steps to reproduce\r\n\r\n1. Include a Vue component inside a Nuxt Content file.\r\n2. Run `nuxt generate`.\r\n\r\n### What is Expected?\r\n\r\nThe build works.\r\n\r\n### What is actually happening?\r\n\r\nThe error `Error: render function or template not defined in component: \u003Ccomponent-name>` is thrown.\r\n",[2043,2044],{"name":1998,"color":1999},{"name":1985,"color":1986},9665,"v2.15.8 breaks Vue components inside Nuxt Content","2023-01-22T15:44:59Z","https://github.com/nuxt/nuxt/issues/9665",0.66177285,{"labels":2051,"number":2057,"owner":1988,"repository":1988,"state":1989,"title":2058,"updated_at":2059,"url":2060,"score":2061},[2052,2055,2056],{"name":2053,"color":2054},"stale","ffffff",{"name":1998,"color":1999},{"name":1985,"color":1986},10129,"SSR doesn't render `v-else` component after component with `v-html`","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10129",0.6619697,{"description":2063,"labels":2064,"number":2066,"owner":1988,"repository":1988,"state":1989,"title":2067,"updated_at":2068,"url":2069,"score":2070},"I'd like to do the following:\r\n\r\n` \u003Cnuxt-link to=\"/\">\r\n \u003Cdiv class=\"preview-text\">\r\n Text\r\n \u003C/div>\r\n \u003Cnuxt-link to=\"/example\">Link\u003C/nuxt-link>\r\n \u003C/nuxt-link>`\r\n\r\nBut I'm getting:\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\nAnd the nested link (/example) is rendering twice.\r\n\r\nAny ideas why? Thanks!\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/c1630\">#c1630\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2065],{"name":1985,"color":1986},1815,"Nested \u003Cnuxt-link> issue","2023-01-18T15:54:46Z","https://github.com/nuxt/nuxt/issues/1815",0.6623645,{"description":2072,"labels":2073,"number":2076,"owner":1988,"repository":1988,"state":1989,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### 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>",[2074,2075],{"name":1998,"color":1999},{"name":1985,"color":1986},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.6661122,{"description":2082,"labels":2083,"number":2085,"owner":1988,"repository":1988,"state":1989,"title":2086,"updated_at":2087,"url":2088,"score":2089},"pages/test.vue:\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv> =PAGE= \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n\r\nlayouts/default.vue:\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxt />\r\n =LAYOUT=\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nthis is a very simple basic page & layout, but when I access localhost:3000/test I can see =LAYOUT= but =PAGE= not rendered, and there is no any error in console\r\n\r\nnuxt: 2.0.0\r\n\r\nin source page I find that \u003CNUXT /> just rendered to \u003CNuxt>\u003C/Nuxt> \r\n\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8353\">#c8353\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2084],{"name":1985,"color":1986},4624,"unable to compile a vue page with no error","2023-01-18T20:06:18Z","https://github.com/nuxt/nuxt/issues/4624",0.6701554,["Reactive",2091],{},["Set"],["ShallowReactive",2094],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"VkOetR_KNLhSKvbOieYcIxl0P62eaJ6E6g86NBoSCCo":-1},"/nuxt/ui/2565"]