\n\u003C/template>\n\n\u003Cscript setup>\nconst searchTerm = ref('');\n\nconst computedResultLimit = computed(() => {\n if (!searchTerm.value) {\n return 5;\n }\n return 20;\n});\n\u003C/script>\n```\n",[3069],{"name":3070,"color":3071},"question","d876e3",2393,"Command Palette: Specific Item Display with Conditional resultLimit Behavior","2024-10-16T09:31:26Z","https://github.com/nuxt/ui/issues/2393",0.75008494,{"description":3078,"labels":3079,"number":3081,"owner":3029,"repository":3044,"state":3045,"title":3082,"updated_at":3083,"url":3084,"score":3085},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[3080],{"name":3041,"color":3042},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.75023,{"description":3087,"labels":3088,"number":3092,"owner":3029,"repository":3029,"state":3045,"title":3093,"updated_at":3094,"url":3095,"score":3096},"So I am the unlucky one who has to work on Christmas holidays and now nuxt has given up on me too :cry: \r\n\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/c2149\">#c2149\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3089],{"name":3090,"color":3091},"2.x","d4c5f9",2474,"Website Down","2023-01-18T15:55:18Z","https://github.com/nuxt/nuxt/issues/2474",0.7505551,{"description":3098,"labels":3099,"number":3102,"owner":3029,"repository":3044,"state":3045,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Environment\n\nOperating System: `Darwin`\nNode Version: `v22.11.0`\nNuxt Version: `3.14.1592`\nCLI Version: `3.16.0`\nNitro Version: `2.10.4`\nPackage Manager: `npm@10.9.0`\nBuilder: -\nUser Config: `default`\nRuntime Modules: `@nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.2, @nuxt/image@1.8.1`\nBuild Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://github.com/makvv4/nuxtui3-avatar-bug-reproduction\n\n### Description\n\nIn the markup we see the correct link to the image, but in the avatar component only a fallback is displayed.\nIn the Network tab, you can see that there are multiple requests made at the same time: one with the correct link, and another request links to the localhost.\n\nThe provider is located in `/providers/my-img-provider.ts`\nAnd config looks like:\n```javascript\nexport default defineNuxtConfig({\n devtools: { enabled: true },\n modules: ['@nuxt/ui', '@nuxt/eslint', '@nuxt/image'],\n css: ['~/assets/css/main.css'],\n\n future: {\n compatibilityVersion: 4,\n },\n\n compatibilityDate: '2024-11-27',\n\n image: {\n providers: {\n myImgProvider: {\n provider: '~~/providers/my-img-provider.ts',\n },\n },\n provider: 'myImgProvider',\n },\n})\n```\n\n### Additional context\n\n\n\n\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3100,3101],{"name":3020,"color":3021},{"name":3041,"color":3042},2857,"[v3][UAvatar] `UAvatar` breaks when using `@nuxt/image` with custom provider","2025-01-11T15:14:06Z","https://github.com/nuxt/ui/issues/2857",0.75330085,{"description":3108,"labels":3109,"number":3110,"owner":3029,"repository":3111,"state":3045,"title":3112,"updated_at":3113,"url":3114,"score":3115},"- [x] Colors & Fonts\n- [x] Landing page (Home)\n- [x] Showcase categories/hero\n- [x] Modules categories/hero\n- [x] Blog categories/hero\n- [x] Support hero/content",[],1305,"nuxt.com","Marketing Update","2023-07-04T10:00:31Z","https://github.com/nuxt/nuxt.com/issues/1305",0.7538299,{"description":3117,"labels":3118,"number":3120,"owner":3029,"repository":3044,"state":3045,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Description\r\n\r\nHey!\r\nIm using an UInput type number and encountered something strange.\r\nIt is not possible to write the number \"1.04\" or \"0.06\". The culprit seems to be the \"0\" after the \".\".\r\nFurther example of working decimal: \"1.14\", 1.56\"\r\nIt works fine if you use \",\" as a comma but my mobile phones number keyboard only provides \".\".\r\n\r\nThe same behvaiour can be tested here:\r\nhttps://ui.nuxt.com/components/input\r\n\r\nIm using Mac and Chrome to test.\r\n\r\nLet me know what you think! :)",[3119],{"name":3020,"color":3021},1722,"Nuxt UI - UInput Type Number - weird behaviour with decimals","2025-03-28T17:59:29Z","https://github.com/nuxt/ui/issues/1722",0.756384,{"description":3126,"labels":3127,"number":3134,"owner":3029,"repository":3111,"state":3045,"title":3135,"updated_at":3136,"url":3137,"score":3138},"",[3128,3131],{"name":3129,"color":3130},"enhancement","1ad6ff",{"name":3132,"color":3133},"responsive","1cd1c6",821,"[Navbar] Add color mode switch in mobile aside nav","2023-02-15T12:31:01Z","https://github.com/nuxt/nuxt.com/issues/821",0.75747406,["Reactive",3140],{},["Set"],["ShallowReactive",3143],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjk1fIcocvbboTKKCc0Nq6bgrH-DE3r-2a9PfSY6TwI8":-1},"/nuxt/ui/2129"]