\n \u003CUSlider v-if=\"index == 'range' && typeof item == 'number'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />\n \u003CUInput v-else :type=\"index\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003Cpre class=\"w-1/2 bg-gray-200 p-4 leading-14\"> {{ state }} \u003C/pre>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst state = ref({}) // ISSUE: Default values are not loaded in the v-model\nconst items = {\n number: 50,\n reset: true, // ISSUE: UInput is not supporting boolean values for v-model\n submit: true, // ISSUE: UInput is not supporting boolean values for v-model\n search: \"search\",\n date: \"2025-04-25\",\n text: \"text\",\n color: \"#ccffcc\",\n button: true, // ISSUE: UInput is not supporting boolean values for v-model\n checkbox: false, // ISSUE: UInput is not supporting boolean values for v-model\n \"datetime-local\": \"2025-04-25T10:49:31\",\n email: \"nobody@gmail.com\",\n file: \"\",\n hidden: \"hidden\",\n image: \"image.svg\",\n month: \"2025-04\",\n password: \"topsecret\",\n radio: true, // ISSUE: UInput is not supporting boolean values for v-model\n range: 50, // Default value is displayed but not loaded in the v-model\n tel: \"0612345678\",\n time: \"10:49:31\",\n url: \"www.chatgpt.com\",\n week: \"2025-W16\"\n}\n// const state = reactive(items) // Workaround for default-value\n\u003C/script>\n```\n\n### Description\n\nI made a small comparison between `UInput` and other components like `UColorPicker` and `USlider` and I stumbled on a couple of issues.\n* `default-value` is not displayed except for `range` and `USlider`\n* `default-value` is never initialized in the `v-model`\n* Booleans are not supported in the `v-model` and I was therefore not able to make them reactive.\n\nWorkaround is to load the default value via the `state`, but that requires an additional step and is therefore not ideal for dynamic forms\n`const state = reactive(items)`\n\nWorkaround for working with booleans, but I am not sure how to apply the `v-model` yet🤔\n`\u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />`\n\n\n### Additional context\n\nDefault values via `default-value`\n\nDefault value via `state`\n\n\n### Logs\n\n```shell-script\n\n```",[2904,2907,2910],{"name":2905,"color":2906},"bug","d73a4a",{"name":2908,"color":2909},"v3","49DCB8",{"name":2911,"color":2912},"triage","ffffff",3983,"nuxt","ui","open","Default values are not loaded in the v-model","2025-05-05T16:31:01Z","https://github.com/nuxt/ui/issues/3983",0.6593486,{"description":2922,"labels":2923,"number":2927,"owner":2914,"repository":2915,"state":2916,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[2924,2925,2926],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.6810169,{"description":2933,"labels":2934,"number":2938,"owner":2914,"repository":2915,"state":2916,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.13.1`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `yarn@1.22.22`\n- Builder: `-`\n- User Config: `compatibilityDate`, `extends`, `modules`, `css`, `app`, `linkChecker`, `build`, `schemaOrg`, `sitemap`, `robots`, `future`, `runtimeConfig`, `imports`, `ui`, `image`, `dayjs`, `prismic`\n- Runtime Modules: `@nuxtjs/prismic@4.1.0`, `nuxt-swiper@2.0.0`, `dayjs-nuxt@2.1.11`, `@nuxt/ui@3.0.0`, `@zadigetvoltaire/nuxt-gtm@0.0.13`, `@nuxtjs/seo@3.0.1`, `@nuxt/scripts@0.11.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0\n\n### Reproduction\n\nnot needed\n\n### Description\n\nThe header with a lot of text in mobile is getting squashed. I believe the problem is the min-h-16 utility.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2935,2936,2937],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},3635,"UModal Header height clipped","2025-03-20T13:20:49Z","https://github.com/nuxt/ui/issues/3635",0.68285966,{"description":2944,"labels":2945,"number":2949,"owner":2914,"repository":2950,"state":2916,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.15.0`\n- Nuxt Version: `3.17.4`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `yarn@1.22.19`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`\n- Runtime Modules: `@nuxt/test-utils@3.19.1`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://github.com/cjpearson/test-utils-issue\n\n### Describe the bug\n\nAfter upgrading to Vue 3.5.15, we have a test where the component is improperly rendered. This is the output of `renderSuspended().html()`\n\n**Before (3.5.14):**\n\n```html\n\u003Cdiv id=\"test-wrapper\">\n \u003Cdiv>\n \u003Ctransition-stub appear=\"false\" persisted=\"false\" css=\"true\">\n \u003Cdialog open=\"\">\u003Cbutton data-testid=\"close-button\"> Close \u003C/button>\n \u003Cdiv>\n \u003Cdiv data-testid=\"dialog-content\"> I am some modal content \u003C/div>\n \u003C/div>\n \u003C/dialog>\n \u003C/transition-stub>\u003Cbutton data-testid=\"btn\">Open\u003C/button>\n \u003C/div>\n\u003C/div>\n```\n\n**After (3.5.15):**\n\n```html\n\u003Cdiv id=\"test-wrapper\">\n \u003Cdiv>\n \u003C!--[object Object]-->\u003Cbutton data-testid=\"btn\">Open\u003C/button>\n \u003C/div>\n\u003C/div>\n```\n\nWhile it's caused by a vue upgrade, I think this may be an issue within the test-utils because when running the application itself, everything seems to work ok.\n\n### Additional context\n\nThere seem to be a couple necessary aspects for this bug to occur:\n\n* There's a component which has a prop of type `Component`\n* The default value for this prop is imported through a barrel file\n\nI've tried narrowing down the changes in Vue 3.5.15 and it looks like [this change](https://github.com/vuejs/core/pull/13245/files) in compiler-sfc is the root cause. \n\n### Logs\n\n```shell-script\n\n```",[2946],{"name":2947,"color":2948},"pending triage","5D08F5",1312,"test-utils","Incorrect rendering with vue 3.5.15 and component props","2025-06-02T13:37:43Z","https://github.com/nuxt/test-utils/issues/1312",0.68942773,{"description":2956,"labels":2957,"number":2965,"owner":2914,"repository":2915,"state":2966,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.4.0, @vueuse/nuxt@10.11.1, @nuxt/ui@2.19.2, @pinia/nuxt@0.5.5, nuxt-echarts@0.2.4\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-8d9s2j?file=app.vue\n\n### Description\n\nThe UInput component does not handle compositionstart and compositionend events, resulting in issues for languages that rely on input composition, such as Chinese (e.g., Pinyin input). Vue’s default behavior for v-model on native input elements ensures that updates are delayed until the composition ends, preventing intermediate values from triggering updates. However, the UInput component currently lacks this mechanism, causing inconsistencies with Vue’s default form handling and leading to unexpected behavior during text composition.\n\n### Additional context\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003Cinput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[2958,2959,2960,2963],{"name":2905,"color":2906},{"name":2911,"color":2912},{"name":2961,"color":2962},"closed-by-bot","ededed",{"name":2964,"color":2962},"stale",2713,"closed","UInput Component Lacks Proper Handling of compositionstart and compositionend","2025-06-18T09:05:41Z","https://github.com/nuxt/ui/issues/2713",0.62305284,{"description":2972,"labels":2973,"number":2976,"owner":2914,"repository":2915,"state":2966,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[2974,2975],{"name":2905,"color":2906},{"name":2908,"color":2909},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6616945,{"description":2982,"labels":2983,"number":2987,"owner":2914,"repository":2915,"state":2966,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v20.12.2\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.1\r\n- Package Manager: pnpm@8.3.1\r\n- Builder: -\r\n- User Config: app, colorMode, ui, css, modules, runtimeConfig, authJs, pinia, nitro, alias, devtools, imports, typescript\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.2.0, @vueuse/nuxt@9.13.0, @hebilicious/authjs-nuxt@0.3.0-beta.2, @nuxtjs/eslint-module@4.1.0, nuxt-monaco-editor@1.2.7, nuxt-lodash@2.5.3, @nuxt/ui@2.14.2\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\nv2.14.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-eqhn2j?file=app.vue\r\n\r\n### Description\r\n\r\nI'm getting multiple new type errors that I wasn't getting before with types that used to be valid. I think this is being caused by an update to `vue-tsc`, however I'm not sure.\r\n\r\nIn the reproduction link you can see the two examples that don't compile. Simply run `npm run typecheck` in the console to get the errors\r\nHere are the minimal examples\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nconst value = ref\u003Cstring | null | undefined>(undefined);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUInput v-model.trim=\"value\" />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n```\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nconst value = ref\u003Cboolean|undefined>();\r\nconst options = [\r\n {\r\n label: 'Yes',\r\n value: true\r\n },\r\n {\r\n label: 'No',\r\n value: false\r\n },\r\n {\r\n label: 'None selected',\r\n value: undefined\r\n }\r\n];\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUSelectMenu\r\n :options=\"options\"\r\n v-model=\"value\"\r\n value-attribute=\"value\" option-attribute=\"label\"\r\n />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'boolean | undefined' is not assignable to type 'string | number | Record\u003Cstring, any> | unknown[] | undefined'.\r\n```\r\n\r\n### Additional context\r\n\r\n\r\n### Logs\r\n\r\n```shell-script\r\napp.vue:14:15 - error TS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n\r\n14 \u003CUInput v-model.trim=\"inputValue\" />\r\n ~~~~~~~~~~\r\n\r\n node_modules/@nuxt/ui/dist/runtime/components/forms/Input.vue.d.ts:244:5\r\n 244 modelValue: string | number;\r\n ~~~~~~~~~~\r\n The expected type comes from property 'modelValue' which is declared here on type 'Partial\u003C{ size: InputSize; ui: any; id: string; icon: string; color: any; type: string; class: any; name: string; modelValue: string | number; leading: boolean; variant: InputVariant; ... 12 more ...; modelModifiers: { ...; }; }> & Omit\u003C...> & Record\u003C...>'\r\n\r\n\r\nFound 1 error in app.vue:14\r\n```\r\n",[2984,2985,2986],{"name":2905,"color":2906},{"name":2961,"color":2962},{"name":2964,"color":2962},1710,"Unable to use boolean values with USelectMenu or null with UInput","2025-06-19T02:12:37Z","https://github.com/nuxt/ui/issues/1710",0.66356295,{"description":2993,"labels":2994,"number":3004,"owner":2914,"repository":2914,"state":2966,"title":3005,"updated_at":3006,"url":3007,"score":3008},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\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: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/content@2.12.1\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nCheckout the project on Stackblitz:\r\n[https://stackblitz.com/edit/nuxt-starter-cjpm2f?file=app.vue](https://stackblitz.com/edit/nuxt-starter-cjpm2f?file=app.vue)\r\nThe input value should be 2, but it remains 1 if you remove the async statement or NuxtLayout, everything will be fixed.\r\n\r\n### Describe the bug\r\n\r\nIt seems something happens in NuxtLayout that breaks v-model behavior *before mount* and prevent it from updating the value of input. if you don't use any async statement or NuxtLayout, everything works fine.\r\n\r\n### Additional context\r\n\r\nIf you don't use v-model and use `:value` and `@input` instead or just print the variable value, everything works file, only v-model is broken.\r\n\r\n### Logs\r\n\r\n_No response_",[2995,2998,3000,3003],{"name":2996,"color":2997},"3.x","29bc7f",{"name":2947,"color":2999},"E99695",{"name":3001,"color":3002},"needs reproduction","FBCA04",{"name":2961,"color":2962},26934,"NuxtLayout breaks v-model behaviour when used after any async statement","2024-05-07T01:49:01Z","https://github.com/nuxt/nuxt/issues/26934",0.66382575,{"description":3010,"labels":3011,"number":3022,"owner":2914,"repository":2914,"state":2966,"title":3023,"updated_at":3024,"url":3025,"score":3026},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.8.0`\r\n- CLI Version: `3.9.1`\r\n- Nitro Version: `2.7.0`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.8.0`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://github.com/TheFlyer1983/nuxt-issue\n\n### Describe the bug\n\nI am getting an issue with a component, that previously worked. But after upgrading my Nuxt to v3.8.0, I keep getting this error whenever I refresh:\r\n\r\n\r\n\r\nI am unable to get past this or debug this because there is no real information in which to use to identify the issue.\n\n### Additional context\n\nThis is causing a major block on upgrading from Nuxt 2 to Nuxt 3, for a business application that is currently live.\n\n### Logs\n\n```shell-script\nI get these logs from my terminal.\r\n\r\n\r\n[[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\r\nconst props = withDefaults(\r\n defineProps<{\r\n disabled?: boolean;\r\n modelValue: object | string | number | null;\r\n small?: boolean;\r\n xSmall?: boolean;\r\n }>(),\r\n {\r\n disabled: false,\r\n small: false,\r\n xSmall: false\r\n }\r\n);\r\n\r\nconst emit = defineEmits<{\r\n (e: 'update:modelValue', value: object | string | number | null): void;\r\n}>();\r\n\r\nconst v = computed({\r\n get: () => props.modelValue,\r\n set: (value) => {\r\n emit('update:modelValue', value);\r\n }\r\n});\r\n</script>\r\n\r\n<template>\r\n <select\r\n v-model=\"v\"\r\n :disabled=\"disabled\"\r\n :class=\"[\r\n 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\r\n {\r\n 'form-select': !small,\r\n 'form-select-small': small,\r\n 'form-select-x-small': xSmall,\r\n 'opacity-50': disabled\r\n }\r\n ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\r\n >\r\n <slot />\r\n </select>\r\n</template>\r\n\u003C/pre>\u003Cbr>\r\nat /components/inputs/StyledSelect.vue] {\r\n cause: {\r\n statusMessage: 'Vite Error',\r\n message: '[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\\n' +\r\n 'const props = withDefaults(\\n' +\r\n ' defineProps<{\\n' +\r\n ' disabled?: boolean;\\n' +\r\n ' modelValue: object | string | number | null;\\n' +\r\n ' small?: boolean;\\n' +\r\n ' xSmall?: boolean;\\n' +\r\n ' }>(),\\n' +\r\n ' {\\n' +\r\n ' disabled: false,\\n' +\r\n ' small: false,\\n' +\r\n ' xSmall: false\\n' +\r\n ' }\\n' +\r\n ');\\n' +\r\n '\\n' +\r\n 'const emit = defineEmits<{\\n' +\r\n \" (e: 'update:modelValue', value: object | string | number | null): void;\\n\" +\r\n '}>();\\n' +\r\n '\\n' +\r\n 'const v = computed({\\n' +\r\n ' get: () => props.modelValue,\\n' +\r\n ' set: (value) => {\\n' +\r\n \" emit('update:modelValue', value);\\n\" +\r\n ' }\\n' +\r\n '});\\n' +\r\n '</script>\\n' +\r\n '\\n' +\r\n '<template>\\n' +\r\n ' <select\\n' +\r\n ' v-model=\"v\"\\n' +\r\n ' :disabled=\"disabled\"\\n' +\r\n ' :class=\"[\\n' +\r\n \" 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\\n\" +\r\n ' {\\n' +\r\n \" 'form-select': !small,\\n\" +\r\n \" 'form-select-small': small,\\n\" +\r\n \" 'form-select-x-small': xSmall,\\n\" +\r\n \" 'opacity-50': disabled\\n\" +\r\n ' }\\n' +\r\n ' ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\\n' +\r\n ' >\\n' +\r\n ' <slot />\\n' +\r\n ' </select>\\n' +\r\n '</template>\\n' +\r\n '\u003C/pre>\u003Cbr>',\r\n stack: '[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\\n' +\r\n 'const props = withDefaults(\\n' +\r\n ' defineProps<{\\n' +\r\n ' disabled?: boolean;\\n' +\r\n ' modelValue: object | string | number | null;\\n' +\r\n ' small?: boolean;\\n' +\r\n ' xSmall?: boolean;\\n' +\r\n ' }>(),\\n' +\r\n ' {\\n' +\r\n ' disabled: false,\\n' +\r\n ' small: false,\\n' +\r\n ' xSmall: false\\n' +\r\n ' }\\n' +\r\n ');\\n' +\r\n '\\n' +\r\n 'const emit = defineEmits<{\\n' +\r\n \" (e: 'update:modelValue', value: object | string | number | null): void;\\n\" +\r\n '}>();\\n' +\r\n '\\n' +\r\n 'const v = computed({\\n' +\r\n ' get: () => props.modelValue,\\n' +\r\n ' set: (value) => {\\n' +\r\n \" emit('update:modelValue', value);\\n\" +\r\n ' }\\n' +\r\n '});\\n' +\r\n '</script>\\n' +\r\n '\\n' +\r\n '<template>\\n' +\r\n ' <select\\n' +\r\n ' v-model=\"v\"\\n' +\r\n ' :disabled=\"disabled\"\\n' +\r\n ' :class=\"[\\n' +\r\n \" 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\\n\" +\r\n ' {\\n' +\r\n \" 'form-select': !small,\\n\" +\r\n \" 'form-select-small': small,\\n\" +\r\n \" 'form-select-x-small': xSmall,\\n\" +\r\n \" 'opacity-50': disabled\\n\" +\r\n ' }\\n' +\r\n ' ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\\n' +\r\n ' >\\n' +\r\n ' <slot />\\n' +\r\n ' </select>\\n' +\r\n '</template>\\n' +\r\n '\u003C/pre>\u003Cbr>\\n' +\r\n 'at /components/inputs/StyledSelect.vue'\r\n },\r\n statusCode: 500,\r\n fatal: false,\r\n unhandled: false,\r\n statusMessage: 'Vite Error',\r\n data: undefined,\r\n __nuxt_error: true\r\n```\n```\n",[3012,3015,3016,3017,3020],{"name":3013,"color":3014},"good first issue","fbca04",{"name":2996,"color":2997},{"name":2905,"color":2906},{"name":3018,"color":3019},"vite","3574D1",{"name":3021,"color":3002},"🔨 p3-minor",23822,"Issue with component since upgrading","2023-10-22T04:39:40Z","https://github.com/nuxt/nuxt/issues/23822",0.66872454,{"description":3028,"labels":3029,"number":3033,"owner":2914,"repository":2915,"state":2966,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3030,3031,3032],{"name":2905,"color":2906},{"name":2908,"color":2909},{"name":2911,"color":2912},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.67194897,["Reactive",3039],{},["Set"],["ShallowReactive",3042],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9UzDiow6WbXmPlxpyGMGpKX1x_WBrgr8iknZvlMfwmI":-1},"/nuxt/ui/4355"]