\n \u003C/UFormField>\n \u003CUFormField\n v-if=\"!authUser\"\n name=\"email\"\n :label=\"$t('label.email')\"\n >\n \u003CUInput\n v-model=\"state.email\"\n icon=\"i-solar-letter-bold-duotone\"\n :placeholder=\"$t('placeholder.enter_email')\"\n @update:model-value=\"state.email = $event || null\"\n />\n \u003C/UFormField>\n \u003CUButton\n block\n type=\"submit\"\n :loading=\"isLoading\"\n :label=\"$t('button.submit')\"\n />\n \u003C/UForm>\n```\n\n### Description\n\nWhy if get error from backend `UForm` set all inputs attr disabled?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2912,2913,2916],{"name":2866,"color":2867},{"name":2914,"color":2915},"needs reproduction","CB47CF",{"name":2902,"color":2903},2612,"if get error from backend `UForm` set all inputs attr disabled","2024-11-13T09:00:48Z","https://github.com/nuxt/ui/issues/2612",0.71451885,{"description":2923,"labels":2924,"number":2928,"owner":2872,"repository":2873,"state":2890,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.5.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.7.1\n- Builder: -\n- User Config: ssr, compatibilityDate, devtools, future, modules, eslint, vite, css\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxt/eslint@1.3.0, @vueuse/nuxt@13.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://playground.vueuse.org/ --> only reproduction if first visit after deploy\n\nRepo:\nhttps://github.com/vueuse/playground.vueuse.org\n\n- pnpm i\n- pnpm build\n- pnpm preview\n- visit localhost:3000 for the first time\n\nRelevant template:\n\n```vue\n \u003CUIcon name=\"i-logos-vueuse\" class=\"size-8\" />VueUse Playground\n \u003CUSelectMenu icon=\"i-logos-vueuse\" :loading=\"loadingVersions\" />\n \u003CUSelectMenu icon=\"i-logos-vue\" :loading=\"loadingVersions\" />\n```\n\n### Description\n\nSometimes (maybe on first page load). Icons are messed up:\n\n\n\nAfter refresh they are fine again:\n\n\n\nThis is might be an upstream bug?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nno errors in console\n```",[2925,2926,2927],{"name":2866,"color":2867},{"name":2902,"color":2903},{"name":2869,"color":2870},3840,"Sometimes icons dont load properly","2025-04-11T12:59:13Z","https://github.com/nuxt/ui/issues/3840",0.71781373,{"description":2934,"labels":2935,"number":2938,"owner":2872,"repository":2873,"state":2890,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.12.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.23.0`\n- Nitro Version: `2.11.6`\n- Package Manager: `pnpm@9.9.0`\n- Builder: `-`\n- User Config: `devtools`, `modules`, `css`, `future`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0`, `@nuxt/eslint@1.2.0`\n- Build Modules: `-`\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/lingering-night-wl8j66\n\n### Description\n\nWhen items have value `null` or `undefined` and click the select menu, app will throw an error. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: Cannot read properties of undefined (reading 'disabled') SelectMenu.vue:379\n at SelectMenu.vue:379:35\n at renderList (runtime-core.esm-bundler.js:2904:16)\n at SelectMenu.vue:1:1\n at renderFnWithContext (runtime-core.esm-bundler.js:692:13)\n at renderSlot (runtime-core.esm-bundler.js:2981:53)\n at ComboboxGroup.vue:38:2\n at renderFnWithContext (runtime-core.esm-bundler.js:692:13)\n at renderSlot (runtime-core.esm-bundler.js:2981:53)\n at ListboxGroup.vue:21:34\n at renderFnWithContext (runtime-core.esm-bundler.js:692:13)\n```",[2936,2937],{"name":2866,"color":2867},{"name":2869,"color":2870},3316,"`USelectMenu`: can not open drop select when options have value `null`","2025-03-15T11:31:45Z","https://github.com/nuxt/ui/issues/3316",0.720731,{"description":2944,"labels":2945,"number":2946,"owner":2872,"repository":2889,"state":2890,"title":2947,"updated_at":2948,"url":2949,"score":2950},"On the [showcase](https://nuxt.com/showcase) page if you change the category and navigate back and forth the displayed showcases are incorrect.\r\n\r\nSteps to reproduce:\r\n\r\n- Open [https://nuxt.com/showcase](https://nuxt.com/showcase)\r\n- Change `category` to `Tech` \r\n- Querystring will change to [https://nuxt.com/showcase?category=Tech](https://nuxt.com/showcase?category=Tech)\r\n\r\n\r\n\r\n- Click on one showcased website and hit the back button to go back to nuxt.com\r\n- The querystring still contains (correctly ) `?category=Tech` - the showcase cards contain the correct tech titles and descriptions, but the images and the urls are not aware anymore that the `Tech` category is still active in the querystring. Navigation is back to `Featured` but the content is still not quite correctly displayed; it is completely mixed up now:\r\n\r\n\r\n\r\n\r\n\r\n\r\n",[],1473,"Selected category in showcase incorrect after navigation","2024-01-09T07:34:45Z","https://github.com/nuxt/nuxt.com/issues/1473",0.72411245,{"description":2952,"labels":2953,"number":2956,"owner":2872,"repository":2873,"state":2890,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.7.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: ssr, imports, devtools, experimental, future, compatibilityDate, alias, runtimeConfig, devServer, typescript, app, css, modules, build, hooks, dayjs, ui\n- Runtime Modules: @nuxt/eslint@1.1.0, @vueuse/nuxt@12.7.0, @nuxt/test-utils/module@3.17.0, dayjs-nuxt@2.1.11, nuxt-svgo@4.0.14, @nuxt/ui@3.0.0-alpha.13, @pinia/nuxt@0.10.1, @pinia/colada-nuxt@0.0.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n@nuxt/ui@3.0.0-alpha.13\n\n### Reproduction\n\nno actions, no styles, no nothing\n\n### Description\n\nno actions, no styles, no nothing\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2954,2955],{"name":2866,"color":2867},{"name":2902,"color":2903},3386,"Nothing works","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3386",0.72429186,{"description":2962,"labels":2963,"number":2970,"owner":2872,"repository":2872,"state":2890,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\r\n\r\nNuxt 3.5\r\nNode 18\r\n\r\n### Reproduction\r\n\r\nSo we have Nitro Cache API documentation https://nitro.unjs.io/guide/cache\r\nAs well as an option to create custom driver for Unstorage: https://unstorage.unjs.io/custom-driver\r\n\r\n\r\n```js\r\n// Creating custom driver\r\nimport { createStorage, defineDriver } from \"unstorage\";\r\n\r\nconst myStorageDriver = defineDriver((options) => {\r\n return {\r\n name: \"my-custom-driver\",\r\n options,\r\n async hasItem(key, _opts) {},\r\n async getItem(key, _opts) {},\r\n async setItem(key, value, _opts) {},\r\n async removeItem(key, _opts) {},\r\n async getKeys(base, _opts) {},\r\n async clear(base, _opts) {},\r\n async dispose() {},\r\n async watch(callback) {},\r\n };\r\n});\r\n\r\nconst storage = createStorage({\r\n driver: myStorageDriver(),\r\n```\r\n\r\nHow to use that driver in Nuxt? Where to register it / import? I tried to put it in plugins, however did not succeed.\r\nBelow solution won't work, nuxt can't find it (unsuprisingly)\r\n```js\r\n// nuxt.config.ts\r\nexport default defineNuxtConfig({\r\n nitro: {\r\n storage: {\r\n cache: {\r\n driver: 'my-custom-driver'\r\n }\r\n }\r\n }\r\n})\r\n```\r\n\r\n### Describe the bug\r\n\r\nWhile in-memory production cache is nice for small-scale apps, in large-scale application we would like to connect to external key-value storage (which driver preset is not predefined in Unstorage, like Redis).\r\n\r\nWe would like to enable page-caching (enabling cache in route rules) in external storage and purge cache with our backend.\r\n\r\nAssuming we successfully created custom cache driver, there is no documentation on how to connect it with Nuxt app (and how nuxt will use it to serve page from cache).\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2964,2967],{"name":2965,"color":2966},"3.x","29bc7f",{"name":2968,"color":2969},"pending triage","E99695",22990,"Cache: Can't use Unstorage custom driver with Nitro Cache in Nuxt 3","2023-09-12T19:42:54Z","https://github.com/nuxt/nuxt/issues/22990",0.7264222,{"description":2976,"labels":2977,"number":2984,"owner":2872,"repository":2872,"state":2890,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Versions\r\n\r\n- v2.14.6\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/s/crazy-browser-fw1wo?file=/components/ArchiveFetcher.vue\r\n\r\n### Steps to reproduce\r\n\r\n``` \r\ndata() {\r\n return {\r\n fetchedPosts: [],\r\n };\r\n },\r\n components: {\r\n //CountriesList,\r\n CountriesList: () => import(\"~/components/CountriesList\"),\r\n },\r\n async fetch() {\r\n if (process.server) {\r\n let url = \"https://jsonplaceholder.typicode.com/posts\";\r\n console.warn(url, \"Archive fetching\");\r\n try {\r\n this.fetchedPosts = await this.$axios.$get(url);\r\n } catch (err) {\r\n return this.$nuxt.error({ statusCode: 404, message: err.message });\r\n }\r\n console.log(this.fetchedPosts); - return array of posts\r\n }\r\n },\r\n mounted() {\r\n console.warn(this.fetchedPosts); - return [];\r\n }, \r\n```\r\n\r\nAsync import component and try to use it with server-side data.\r\n\r\n### What is Expected?\r\nExpected the same behavior as default components import, without remounting\\refetching on the client.\r\n\r\n### What is actually happening?\r\nWhen we use such construction (async components import) - the component is filling with data on the server-side, but then it looks like remounting on the client without any data and trying to fetch it again.\r\nWhen I import a component in the default way, it works as expected, without losing data on the client.\r\n\r\nI hope I describe the issue clearly enough, but let me know if you need any additional info.",[2978,2980,2981],{"name":2979,"color":2870},"stale",{"name":2968,"color":2969},{"name":2982,"color":2983},"2.x","d4c5f9",8513,"Component remounting and refetching data on client side in case of usage async components import","2023-01-22T15:38:24Z","https://github.com/nuxt/nuxt/issues/8513",0.72820395,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6WINQodHUIy6NqiBLLSgKlU4Vg-NBcjow4DH9MqK3AY":-1},"/nuxt/ui/3706"]