\n\u003C/template>\n```\n\nSelectMenu does not display the label associated to the falsy value \"0\":\n\n\nThe list is populated with both values:\n\n\nThe label associated to the truthy value \"1\" is displayed as expected:\n\n\n### Description\n\nAll falsy values are not displayed anymore since v2.20.0 due to the rework of the computed `label` in the SelectMenu component.\n\nHere is the definition of this computed in `/src/runtime/components/form/SelectMenu.vue`:\n```\nconst label = computed(() => {\n if (!props.modelValue) return null\n\n if (Array.isArray(props.modelValue) && props.modelValue.length) {\n return `${props.modelValue.length} selected`\n } else if (['string', 'number'].includes(typeof props.modelValue)) {\n return props.valueAttribute ? accessor(selected.value, props.optionAttribute) : props.modelValue\n }\n\n return accessor(props.modelValue as Record\u003Cstring, any>, props.optionAttribute)\n})\n```\n\n**The component should treat `0`, `\"\"` and `false` as \"acceptable\" labelled values.**\n\nI believe the first condition should be either :\n`if(props.modelValue == null) return null` \nOr:\n`if(props.modelValue === null || props.modelValue === undefined) return null` \n\n### Additional context\n\nI will try to find some time to create a pull request if this is accepted as an issue. Not sure I can manage to do it short-term though.\n\n### Logs\n\n```shell-script\n\n```",[2001,2004],{"name":2002,"color":2003},"bug","d73a4a",{"name":1988,"color":1989},3132,"SelectMenu label not displayed for falsy values","2025-01-17T15:36:46Z","https://github.com/nuxt/ui/issues/3132",0.7305455,{"description":2011,"labels":2012,"number":2013,"owner":1991,"repository":2014,"state":1993,"title":2015,"updated_at":2016,"url":2017,"score":2018},"https://github.com/guidepup/guidepup",[],787,"test-utils","screen reader driver","2024-03-17T21:40:20Z","https://github.com/nuxt/test-utils/issues/787",0.7306928,{"description":2020,"labels":2021,"number":2022,"owner":1991,"repository":2023,"state":1993,"title":2024,"updated_at":2025,"url":2026,"score":2027},"Hi, hope you're all doing well!\r\n\r\nI ran into an issue using `@nuxt/ui` which now uses `@nuxt/icon` under the hood (used to work when icon collection names could be specified as nuxt/ui module args even tho i had to add a ts-ignore as it wasn't referenced in the enum type), I am using a custom iconify collection i built which goes by\r\n```json filename=\"package.json\"\r\n\"@iconify-json/as\": \"npm:@my-org-name/my-icon-collection@^0.0.2\",\r\n```\r\nin my package.json which isn't referenced in\r\nhttps://github.com/nuxt/icon/blob/main/src/collection-names.ts\r\nthus making it uncompatible with `@nuxt/icon`.\r\nI think the issue comes from the usage of `collectionNames` there (as it seems we only values are only read if they are part of the underlying array):\r\nhttps://github.com/nuxt/icon/blob/cc14fe49b19fce023ba6f049984317492043c9ab/src/collections.ts#L72-L73\r\nWould it be possible further expand the compatibility to include custom collections? (and eventually check if these are installed print an error on the logger if it isn't the case)\r\n\r\nNOTE: It seems to work when using this configuration (note SSR isn't set to false which is a constraint I have)\r\n```ts filename=\"nuxt.config.ts\"\r\nicon: {\r\n serverBundle: {\r\n collections: [\r\n 'as'\r\n ]\r\n }\r\n}\r\n```\r\nbut it the specific project is using this piece of config\r\n```ts filename=\"nuxt.config.ts\"\r\n[...]\r\nssr: false, // SSR forced to false\r\nicon: {\r\n provider: 'server', // Tried with and without this\r\n serverBundle: {\r\n collections: [\r\n 'as'\r\n ]\r\n }\r\n}\r\n```\r\n\r\nSorry if it is a bit long, I tried my best to keep it pleasant to read though. Thank you in advance! :)\r\n",[],252,"icon","Custom collections aren't recognised","2024-09-10T10:57:04Z","https://github.com/nuxt/icon/issues/252",0.7372105,{"description":2029,"labels":2030,"number":2031,"owner":1991,"repository":2032,"state":1993,"title":2033,"updated_at":2034,"url":2035,"score":2036},"### Describe the feature\n\nI found, how to deploy nuxt 2 app into gcp app engine. But there is no doc about nuxt 3\n\n### Additional information\n\n- [ ] 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).",[],1764,"nuxt.com","deploy nuxt 3 on gcp appengine","2025-01-22T09:58:41Z","https://github.com/nuxt/nuxt.com/issues/1764",0.74933845,{"description":2038,"labels":2039,"number":2042,"owner":1991,"repository":1992,"state":1993,"title":2043,"updated_at":2044,"url":2045,"score":2046},"### Environment\n\nDocumentation error.\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\nNot applicable\n\n### Description\n\nUnder this [subheading](https://ui.nuxt.com/components/form#input-events), there is a link to a file [here](https://github.com/nuxt/ui/blob/dev/docs/components/content/examples/FormExampleElements.vue) but it does not have the key `validate-on` on any of the components. I believe that it should be there.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2040,2041],{"name":2002,"color":2003},{"name":1988,"color":1989},2812,"[docs] UForm's validate-on example is incorrect","2024-11-30T18:18:23Z","https://github.com/nuxt/ui/issues/2812",0.75045115,{"description":2048,"labels":2049,"number":2054,"owner":1991,"repository":2014,"state":2055,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.20.2\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@3.6.1\r\n- Builder: -\r\n- User Config: devtools, build, modules, fonts, colorMode, i18n, logLevel, nitro, sentry, runtimeConfig\r\n- Runtime Modules: nuxt-zod-i18n@latest, @nuxtjs/i18n@8.3.1, @nuxt/ui@^2.15.2, @nuxt/test-utils/module@3.12.1, @nuxt/fonts@latest, @vueuse/nuxt@10.9.0\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nJust create a simple component with :\r\n\r\n```\r\n\u003Cscript lang=\"ts\" setup>\r\nconst error = ref(false);\r\n\u003C/script>\r\n```\r\n\r\nSimple test \r\n\r\n```\r\nit('mount', async () => {\r\n const component = await mountSuspended(TheFooter);\r\n expect(component.html()).toMatchSnapshot();\r\n });\r\n```\n\n### Describe the bug\n\n```\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ Proxy.clonedComponent.render ../../../node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:131:44\r\n 129| renderContext[key] = passedProps[key];\r\n 130| }\r\n 131| return render.call(this, renderContext, ...args);\r\n | ^\r\n 132| } : void 0,\r\n 133| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot ../../../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:885:16\r\n ❯ ReactiveEffect.componentUpdateFn [as fn] ../../../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5969:46\r\n ❯ ReactiveEffect.run ../../../node_modules/@vue/reactivity/dist/reactivity.cjs.js:181:19\r\n ❯ instance.update ../../../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6100:16\r\n ❯ setupRenderEffect ../../../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6110:5\r\n ❯ ../../../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1639:9\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2050,2051],{"name":2002,"color":2003},{"name":2052,"color":2053},"pending triage","5D08F5",835,"closed","Test fail if component contain const error = ref(false);","2024-05-08T21:48:21Z","https://github.com/nuxt/test-utils/issues/835",0.69051486,{"description":2061,"labels":2062,"number":2067,"owner":1991,"repository":1992,"state":2055,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2063,2064],{"name":2002,"color":2003},{"name":2065,"color":2066},"v3","49DCB8",3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.71697325,{"description":2073,"labels":2074,"number":2077,"owner":1991,"repository":1992,"state":2055,"title":2078,"updated_at":2079,"url":2080,"score":2081},"### Environment\n\n\n\nI get this error anytime I try and use \u003CUInput /> even without any other code.\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n`\u003Ctemplate>\n \u003CUContainer>\n \u003CUForm :schema=\"schema\" :state=\"state\" class=\"space-y-4\" @submit=\"onSubmit\">\n \u003CUFormField label=\"Code\" name=\"Code\"\n >\u003CUInput v-model=\"state.code\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { z } from 'zod';\nimport type { FormSubmitEvent } from '#ui/types';\n\nconst supabase = useSupabaseClient();\nconst toast = useToast();\n\n//Form\nconst schema = z.object({\n code: z.string().min(3),\n});\n\ntype Schema = z.output\u003Ctypeof schema>;\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n code: undefined,\n});\n\nasync function onSubmit(event: FormSubmitEvent\u003CSchema>) {\n toast.add({\n title: 'Success',\n description: 'The form has been submitted.',\n color: 'success',\n });\n console.log(event.data);\n}\n\u003C/script>\n`\n\n### Description\n\nUInput causes an error\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2075,2076],{"name":2002,"color":2003},{"name":2065,"color":2066},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.73504436,{"description":2083,"labels":2084,"number":2089,"owner":1991,"repository":1992,"state":2055,"title":2090,"updated_at":2091,"url":2092,"score":2093},"### Description\n\nIs it possible to define the same configuration that is defined in app.config, inside a component.\n\nNow it seems that you can only define the slots, or class when there are no slots.",[2085,2088],{"name":2086,"color":2087},"question","d876e3",{"name":2065,"color":2066},3681,"Define variants inside a component","2025-03-26T09:51:36Z","https://github.com/nuxt/ui/issues/3681",0.73538077,["Reactive",2095],{},["Set"],["ShallowReactive",2098],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"OQt3iRe9ENdNmLiTfAqndqySr9wJXp5e-lq6l6s1Cxc":-1},"/nuxt/ui/2221"]