` component.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Invalid prop: custom validator check failed for prop \"color\". \n at \u003CProgress key=1 color=\"neutral\" size=\"xl\" ... > \n```",[2887,2888],{"name":2870,"color":2871},{"name":2876,"color":2877},3407,"UProgress missing color type","2025-03-02T15:30:03Z","https://github.com/nuxt/ui/issues/3407",0.6994404,{"description":2895,"labels":2896,"number":2907,"owner":2860,"repository":2860,"state":2908,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### 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_",[2897,2900,2901,2904],{"name":2898,"color":2899},"3.x","29bc7f",{"name":2857,"color":2858},{"name":2902,"color":2903},"needs reproduction","FBCA04",{"name":2905,"color":2906},"closed-by-bot","ededed",26934,"closed","NuxtLayout breaks v-model behaviour when used after any async statement","2024-05-07T01:49:01Z","https://github.com/nuxt/nuxt/issues/26934",0.6646716,{"description":2914,"labels":2915,"number":2919,"owner":2860,"repository":2860,"state":2908,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: pnpm@8.9.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-4cyshx?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\ninput Use v-model two-way binding, when change the v-model to :value, the two-way binding is still effective, need to refresh the page, then it will be normal.\r\n\r\n### Logs\r\n\r\n_No response_",[2916,2917,2918],{"name":2898,"color":2899},{"name":2857,"color":2858},{"name":2902,"color":2903},23688,"input Use v-model bidirectional binding hot update exception","2023-10-17T08:33:12Z","https://github.com/nuxt/nuxt/issues/23688",0.6776127,{"description":2925,"labels":2926,"number":2929,"owner":2860,"repository":2879,"state":2908,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.3.0\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.1, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.2.0, @nuxtjs/i18n@9.5.4, nuxt-security@2.2.0, @nuxt/ui@3.1.2\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/sharp-christian-kzdxt9?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nStarting from v3.1.2, using the [built-in v-model-modifiers](https://vuejs.org/guide/essentials/forms.html#modifiers) produces type errors. They are still working tho, so its only a type issue.\n\nReproduction:\n1. Open provided link\n2. Run `pnpx nuxi typecheck`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n➜ workspace git:(master) ✗ pnpx nuxi typecheck\nPackages: +1\n+\nProgress: resolved 1, reused 1, downloaded 0, added 1, done\nℹ Nuxt Icon server bundle mode is set to local 11:09:23 AM\n✔ Nuxt Icon discovered local-installed 2 collections: lucide, simple-icons 11:09:25 AM\nℹ Running with compatibility version 4 nuxt 11:09:25 AM\napp/pages/index.vue:8:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: number) => any) | undefined; ... 24 more ...; modelValue?: number | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n8 \u003CUInput v-model.number=\"myNumber\" type=\"number\" />\n ~~~~~~~\n\napp/pages/index.vue:9:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: string) => any) | undefined; ... 24 more ...; modelValue?: string | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n9 \u003CUInput v-model.lazy=\"myText\" />\n ~~~~~\n\n\nFound 2 errors in the same file, starting at: app/pages/index.vue:8\n\n\n ERROR Process exited with non-zero status (2) 11:09:41 AM\n\n at R._waitForOutput (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/main.mjs:508:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Object.run (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/typecheck.mjs:91:9)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1767:16)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1758:11)\n at async runMain$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1896:7) \n\n\n\n ERROR Process exited with non-zero status (2)\n```",[2927,2928],{"name":2870,"color":2871},{"name":2873,"color":2874},4166,"Built-in v-model modifiers produce type errors with v3.1.2","2025-05-22T12:51:25Z","https://github.com/nuxt/ui/issues/4166",0.6804629,{"description":2935,"labels":2936,"number":2938,"owner":2860,"repository":2860,"state":2908,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.10.0`\n- Nuxt Version: `3.14.1592`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.7.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ynphxo8p?file=app.vue\n\n### Describe the bug\n\nThe `defineModel` function works as expected in Vue's playground but does not work in a Nuxt project. I copied the exact same code from Vue's playground into my Nuxt project, but it fails to function correctly.\n\n### Expected Behavior\nThe `defineModel` function should work as it does in [Vue's playground](https://play.vuejs.org/#eNqFUtFKwzAU/ZWYl06YLbK30Q10DFSYigq+5KW0t11mmoQknZPSf/cm3eqEsT0l555zuefmpKV3WsfbBuiUpjY3XDtiwTV6ziSvtTKOLNZcFKQ0qiZRnATkG6JB0BIDJen2kp5iMlfSOlLbisw8P4oeQAhFPpURxVV0zWSa9PNwEgIHtRaZA0SEpOvbeduG5q5LE0Sh2jvZ3tSqADFjFHlGSYJkmhz10zF1FseXvIo3VklcrfX9jOaq1lyAedGOoz1GpyQwnsvQ3fdTqDnTwPhQz9eQf52ob+zO1xh9NWDBbIHRgXOZqcD19PL9GXZ4H0h03whUnyHfwCrReI+97L6RBdo+0gW3j+H9uaw+7HLnQNrDUt6oV3ZBzyhmsjiz+p/dSTwJfUx2+IpD1ic+xz5enwQGXEDJJaw8Gl2I1upMzlc/hEvdOBR6SNKAjqP1J6P/o6XdL11L5h4=), allowing two-way binding between the component's model and the parent.\n\n### Actual Behavior\nThe `defineModel` function does not behave as expected, the value of the input is not updating.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2937],{"name":2857,"color":2858},30205,"defineModel Not Working in Nuxt 3 Despite Working in Vue's Playground","2024-12-09T13:38:08Z","https://github.com/nuxt/nuxt/issues/30205",0.6812551,{"description":2944,"labels":2945,"number":2952,"owner":2860,"repository":2860,"state":2908,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: devtools, modules, runtimeConfig, devServer, plugins, vue, app, typescript, compatibilityDate, hooks\n- Runtime Modules: @nuxt/eslint@0.7.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-95rtqeeh?file=pages%2Fpage2.client.vue\n\n### Describe the bug\n\nWhen the value of a variable is immediately updated within a Promise callback in the setup function as shown below, the change is not reflected in the v-model of the input.\nThis issue only occurs when running in CSR mode, such as in index.client.vue.\nIt does not occur when running the exact same source code in index.vue.\nAdditionally, this issue does not occur in Vue projects that do not use Nuxt.\n\n```vue\n\u003Cscript setup>\nconst msg = ref('')\n\nmsg.value = 'Changed1' // OK\n\nPromise.resolve().then(() => {\n msg.value = 'Changed2' // NG (not reflect for v-model)\n})\n\nsetTimeout(() => {\n msg.value = 'Changed3' // OK\n}, 2000)\n\u003C/script>\n\n\u003Ctemplate>\n msg: {{ msg }}\n \u003Cinput v-model=\"msg\" />\n\u003C/template>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2946,2949],{"name":2947,"color":2948},"upstream-bug","B60205",{"name":2950,"color":2951},"✨ good reproduction","fbca04",30590,"Variable changes are not reflected in v-model in certain case","2025-02-09T18:08:58Z","https://github.com/nuxt/nuxt/issues/30590",0.68592817,{"description":2958,"labels":2959,"number":2965,"owner":2860,"repository":2860,"state":2908,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.18.0`\r\n- Nuxt Version: `2.15.8`\r\n- Nitro Version: `-`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `webpack`\r\n- User Config: `target`, `head`, `server`, `css`, `plugins`, `router`, `components`, `buildModules`, `styleResources`, `modules`, `axios`, `proxy`, `privateRuntimeConfig`, `build`, `vue`\r\n- Runtime Modules: `@nuxtjs/axios@5.13.6`\r\n- Build Modules: `@nuxtjs/eslint-module@3.1.0`, `@nuxtjs/style-resources@1.2.1`\r\n\n\n### Reproduction\n\nOpen link in either IE11 . Open the developer tools and click on console tab. Script error should appear in console.\n\n### Describe the bug\n\nIE11 receive a script error which halts the app's progress in loading\r\nfunction* is not escaped when building the project\r\n\n\n### Additional context\n\n\r\n\r\n\r\nfunction* Display error\r\n\r\nThis is my configuration\r\n\r\n\n\n### Logs\n\n_No response_",[2960,2961,2964],{"name":2857,"color":2858},{"name":2962,"color":2963},"2.x","d4c5f9",{"name":2902,"color":2903},19633,"Nuxt 2.15.8 modern build issues on IE11/Edge (function* unescaped)","2024-06-30T09:22:00Z","https://github.com/nuxt/nuxt/issues/19633",0.6902165,{"description":2971,"labels":2972,"number":2976,"owner":2860,"repository":2860,"state":2908,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n npx nuxi info\r\nNuxi 3.4.2 22:26:20\r\n 22:26:22\r\nRootDir: ***\r\nNuxt project info: 22:26:22\r\n\r\n------------------------------\r\n- Operating System: Windows_NT 22:24:03\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.4.2\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@8.19.2\r\n- Builder: vite\r\n- User Config: nitro, runtimeConfig, extends, build, modules, colorMode, tailwindcss, auth, elementPlus\r\n- Runtime Modules: @nuxtjs/color-mode@3.2.0, unplugin-icons/nuxt, @sidebase/nuxt-auth@0.4.4, @element-plus/nuxt@1.0.4, @nuxtjs/tailwindcss@6.6.6\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nSorry i cannot give the link. It's my online project and it seems not a code problem.\n\n### Describe the bug\n\ngot an error about ' At least one \u003Ctemplate> or \u003Cscript> is required in a single file component when upgraged to 3.4.2 from 3.4.1.\r\n\r\nEverythinkg works fine in 3.4.1.\r\n\r\nI checked all my vue component. There has no empty file.\r\n\r\nso where the msg prompt from. \n\n### Additional context\n\n\r\n\n\n### Logs\n\n_No response_",[2973,2974,2975],{"name":2898,"color":2899},{"name":2857,"color":2858},{"name":2902,"color":2903},20530,"upgraged to 3.4.2 from 3.4.1 got an error about ' At least one \u003Ctemplate> or \u003Cscript> is required in a single file component.","2023-04-26T15:16:00Z","https://github.com/nuxt/nuxt/issues/20530",0.6910656,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1rnvr1fyPzj37UDFbU1B_GSuRayvfltBxDU9WsgGpNw":-1},"/nuxt/ui/4232"]