\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",[3179,3180,3181],{"name":3135,"color":3136},{"name":3167,"color":3168},{"name":3170,"color":3168},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.6644967,{"description":3188,"labels":3189,"number":3193,"owner":3144,"repository":3194,"state":3157,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.16.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `runtimeConfig`, `ssr`, `alias`, `compatibilityDate`, `devtools`, `css`, `vite`, `modules`\n- Runtime Modules: `@nuxt/test-utils/module@3.19.1`\n- Build Modules: `-`\n\n### Reproduction\n\n```json\n//package.json\n{\n \"name\": \"dummy-repo\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"test\": \"vitest\",\n },\n \"dependencies\": {\n \"nuxt\": \"^3.17.5\",\n \"vue\": \"^3.5.16\",\n },\n \"devDependencies\": {\n \"@nuxt/test-utils\": \"^3.19.1\",\n \"happy-dom\": \"^17.6.3\",\n \"vitest\": \"^3.2.3\"\n }\n}\n```\n\n```ts\n//nuxt.config.ts\nexport default defineNuxtConfig({\n ...\n modules: [\n '@nuxt/test-utils/module'\n ]\n})\n```\n\n```ts\n//vitest.config.ts\nimport { configDefaults } from 'vitest/config';\nimport { defineVitestConfig } from '@nuxt/test-utils/config';\nimport vue from '@vitejs/plugin-vue';\n\nexport default defineVitestConfig({\n test: {\n ...\n projects: [\n ...\n {\n plugins: [vue()],\n test: {\n environmentOptions: {\n // nuxt: { // purposely commented out\n // url: 'http://localhost:3000',\n // other properties...\n // }\n },\n include: [\n 'tests/app.test.ts', //With dummy app.vue it can be empty template\n ],\n name: 'Nuxt Environment',\n globals: true,\n environment: 'nuxt',\n },\n },\n ],\n },\n})\n``\n\n### Describe the bug\n\n```bash\n# run\nnpm run test\n```\nResults in:\n\n```bash\nTypeError: Cannot read properties of undefined (reading 'url') # checking this\n ❯ Object.setup node_modules/@nuxt/test-utils/dist/vitest-environment.mjs:177:31\n ❯ withEnv node_modules/vitest/dist/chunks/runBaseTests.Dd85QTll.js:82:32\n ❯ run node_modules/vitest/dist/chunks/runBaseTests.Dd85QTll.js:109:8\n ❯ runBaseTests node_modules/vitest/dist/chunks/base.Cg0miDlQ.js:32:2\n ❯ ForksBaseWorker.executeTests node_modules/vitest/dist/workers/forks.js:29:4\n ❯ execute node_modules/vitest/dist/worker.js:108:3\n ❯ onMessage node_modules/tinypool/dist/entry/process.js:39:18\n```\n\nIn line `Object.setup node_modules/@nuxt/test-utils/dist/vitest-environment.mjs:177:31` seeing this `environmentOptions?.nuxt.url ?? \"http://localhost:3000\",`\n\nI believe `nuxt` could use the help of question mark, so that `http://localhost:3000` can be reached.\n\nSo change the line to `environmentOptions?.nuxt?.url ?? \"http://localhost:3000\",`\n\n### Note on Documention\n\nI see one of the guys constantly saying \"Just follow the documentation\"\nThe documentation specifically says, it can be added [OPTIONALLY](https://nuxt.com/docs/getting-started/testing#using-a-nuxt-runtime-environment)\n```\nexport default defineVitestConfig({\n test: {\n environment: 'nuxt',\n // you can optionally set Nuxt-specific environment options\n // environmentOptions: {\n // nuxt: {\n // rootDir: fileURLToPath(new URL('./playground', import.meta.url)),\n // domEnvironment: 'happy-dom', // 'happy-dom' (default) or 'jsdom'\n // overrides: {\n // // other Nuxt config you want to pass\n // }\n // }\n // }\n }\n})\n```\nThe source code currently makes us doing that mandatorily.\n\nSame thing with the next line.\n\n`environmentOptions?.nuxtRuntimeConfig.app?.baseURL || \"/\"`\n\n```bash\nTypeError: Cannot read properties of undefined (reading 'app')\n```\n\nLet me know, what I can add as a work around, because the documentation doesn't even have anything on the optional side.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3190],{"name":3191,"color":3192},"pending triage","5D08F5",1326,"test-utils","Cannot read url of undefined","2025-08-05T11:07:29Z","https://github.com/nuxt/test-utils/issues/1326",0.6796179,{"description":3200,"labels":3201,"number":3204,"owner":3144,"repository":3145,"state":3157,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.2.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.4\n- Package Manager: bun@1.2.17\n- Builder: -\n- User Config: css, modules, nitro, i18n, imports, runtimeConfig, icon, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@10.0.6, @nuxt/ui-pro@3.3.1, @nuxt/eslint@1.9.0, @nuxtjs/html-validator@2.1.0, @nuxt/image@1.11.0, @vueuse/nuxt@13.7.0, @artmizu/nuxt-prometheus@2.5.2, @nuxtjs/seo@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.1\n\n### Reproduction\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(\"\");\nconst items: Array\u003Cstring | number> = [1, \"2\", 3];\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUForm :state=\"value\" class=\"flex max-w-72 flex-col space-y-4 py-8\">\n \u003CUFormField label=\"UInputMenu\">\n \u003CUInputMenu v-model=\"value\" :items placeholder=\"UInputMenu\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelect\">\n \u003CUSelect v-model=\"value\" :items placeholder=\"USelect\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelectMenu\">\n \u003CUSelectMenu v-model=\"value\" :items placeholder=\"USelectMenu\" />\n \u003C/UFormField>\n \u003C/UForm>\n\u003C/template>\n```\n\n### Description\n\nAfter updating to version 3.3.1, the InputMenu, Select and SelectMenu component's placeholder value is not shown, if the value is not found in the items array. In version 3.3.0 the placeholder correctly shows up.\n\nNuxt UI 3.3.0\n\u003Cimg width=\"350\" height=\"300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b0937d4-7640-4277-8169-ff192bc01d97\" />\n\nNuxt UI 3.3.1\n\u003Cimg width=\"410\" height=\"285\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3d744e11-748b-4b3c-a236-fcee8fdcd765\" />\n\n\u003Cimg width=\"395\" height=\"298\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ac7be307-ca5c-4957-a2fb-5721eebdea07\" />\n\nIf the v-model is `undefined` it works just like in 3.3.0, however in my projects I feel like that's not always achievable because of type definitions.\nI know I could set the default value to one of the items' values, but what if I don't want to populate the component by default and just show the placeholder? \nFor this to work in version 3.3.1 I'd have to loosen up the type definitions, so that required fields are not required anymore, which is wrong and I don't feel like I should have to do to keep the behavior of a UI component. \n\nShouldn't we have an exception for falsy values that are sometimes used as default values (empty string, 0...), so the placeholder can be shown without having to explicitly have `undefined` as the default value?\n\n### Additional context\n\nI haven't dug that deep, but I think #4689 introduced this behavior to these components. \n\n### Logs\n\n```shell-script\n\n```",[3202,3203],{"name":3135,"color":3136},{"name":3138,"color":3139},4812,"[InputMenu,Select,SelectMenu] Placeholder not showing in v3.3.1, if item is not found and default value is not undefined or null","2025-08-27T14:42:51Z","https://github.com/nuxt/ui/issues/4812",0.67982876,{"description":3210,"labels":3211,"number":3220,"owner":3144,"repository":3144,"state":3157,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Environment\r\n\r\nNuxt project info: 20:48:43\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.18.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: pnpm@8.7.6\r\n- Builder: -\r\n- User Config: modules, build, vite, experimental, pinia, piniaPersistedstate, css, colorMode, nitro, app, pwa, devtools\r\n- Runtime Modules: @vueuse/nuxt@10.5.0, @pinia/nuxt@0.5.1, @nuxtjs/color-mode@3.3.0, @vite-pwa/nuxt@0.1.1, @unocss/nuxt@0.57.1, @nuxtjs/device@3.1.1, @formkit/auto-animate/nuxt@0.8.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/besscroft/kamera\r\n\r\n### Describe the bug\r\n\r\nI specified preset: 'vercel' in the nuxt.config.ts file. Every time I push the code and vercel is redeployed, I will encounter this error when accessing the website. I can also encounter similar errors at https://ui.nuxt.com/getting-started/roadmap, but mine is 500 undefind is not an object (evaluating 'e.entries'), encountered in nuxt ui The error reported is 500 Cannot read properties of undefined (reading 'preference'). I asked my friends to visit the same website and found that most of them had similar problems. It appears on chrome, safari, and firefox. When I press Ctrl + F5, I can reload the page and access it normally. I have been using Nuxt3 for almost a year and this problem is a recent one and has not occurred before. This is also the first time I have no clue when facing Nuxt3 errors, so is there any solution? Maybe I can try other ways to troubleshoot.\r\n\r\nFinally, thanks to the Nuxt team and community for their hard work!\r\n\r\n### Additional context\r\n\r\nSimilar to the error in the picture, but my error is 500 undefind is not an object (evaluating 'e.entries'), and it's the entire page.\r\n\r\n\r\n\r\n### Logs\r\n\r\n```shell-script\r\nTypeError: Cannot read properties of undefined (reading 'e.entries')\r\n```\r\n",[3212,3215,3217],{"name":3213,"color":3214},"3.x","29bc7f",{"name":3191,"color":3216},"E99695",{"name":3218,"color":3219},"needs reproduction","FBCA04",24089,"500 undefind is not an object (evaluating 'e.entries')","2023-12-06T20:18:23Z","https://github.com/nuxt/nuxt/issues/24089",0.6800583,{"description":3226,"labels":3227,"number":3236,"owner":3144,"repository":3144,"state":3157,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: ^3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@7.17.0\r\n- Builder: webpack\r\n- User Config: builder, webpack\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-6ue8jc?file=nuxt.config.ts\n\n### Describe the bug\n\nNuxt has [a schema](https://github.com/nuxt/nuxt/blob/main/packages/schema/src/config/webpack.ts#L154-L163) of `vue-loader` options that [partially matches](https://github.com/vuejs/vue-loader/blob/main/src/index.ts#L32-L62) `vue-loader`. \r\n\r\nFor example, you can enable experimental features like Vue 3.3 `defineModel` in `webpack.loaders.vue`, but TypeScript won't recognize it as a valid property. However, if you ignore the error squiggles, it does work.\r\n\n\n### Additional context\n\nMentioned in https://github.com/nuxt/nuxt/pull/21303#issuecomment-1574295022\n\n### Logs\n\n```shell-script\n'{ defineModel: true; }' is not assignable to type '{ productionMode?: boolean | undefined; transformAssetUrls?: { video?: string | undefined; source?: string | undefined; object?: string | undefined; embed?: string | undefined; } | undefined; compilerOptions?: { ...; } | undefined; }'.\r\n Object literal may only specify known properties, and 'defineModel' does not exist in type '{ productionMode?: boolean | undefined; transformAssetUrls?: { video?: string | undefined; source?: string | undefined; object?: string | undefined; embed?: string | undefined; } | undefined; compilerOptions?: { ...; } | undefined; }'.(2322)\n```\n",[3228,3231,3234,3235],{"name":3229,"color":3230},"good first issue","fbca04",{"name":3232,"color":3233},"types","2875C3",{"name":3213,"color":3214},{"name":3135,"color":3136},21332,"Extend vue-loader option types ","2023-06-04T22:07:55Z","https://github.com/nuxt/nuxt/issues/21332",0.68039906,{"description":3242,"labels":3243,"number":3246,"owner":3144,"repository":3145,"state":3157,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.3.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n1. Create a new project with: `pnpx nuxi@latest init -t ui3 nuxt-ui3`\n2. Add the following dependencies in `package.json`\n```json\n{\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\",\n \"lint\": \"eslint .\",\n \"lint:fix\": \"eslint --fix .\"\n },\n \"dependencies\": {\n \"@iconify-json/lucide\": \"^1.2.16\",\n \"@nuxt/ui\": \"3.0.0-alpha.10\",\n \"@nuxt/ui-pro\": \"3.0.0-alpha.10\",\n \"nuxt\": \"^3.15.0\"\n },\n \"devDependencies\": {\n \"@nuxt/devtools\": \"latest\",\n \"@nuxt/eslint\": \"^0.7.2\",\n \"eslint\": \"^9.15.0\",\n \"typescript\": \"^5.7.2\"\n }\n}\n```\n\n3. Add following in `nuxt.config.ts`\n```ts\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n devtools: { enabled: true },\n extends: [\"@nuxt/ui-pro\"],\n modules: [\"@nuxt/ui\", \"@nuxt/eslint\"],\n css: [\"~/assets/css/main.css\"],\n\n future: {\n compatibilityVersion: 4,\n },\n\n compatibilityDate: \"2024-11-27\",\n});\n```\n\n4. Got the following error\n```bash\n> nuxt-app@ dev /Users/ayush/Projects/NodeProjects/nuxt-ui3\n> nuxt dev\n\nNuxt 3.15.0 with Nitro 2.10.4 2:17:28 PM\n\n ERROR Cannot read properties of undefined (reading 'options') 2:17:28 PM\n\n at Object.normalizedModule [as config] (node_modules/.pnpm/@nuxt+kit@3.15.0_magicast@0.3.5_rollup@4.29.1/node_modules/@nuxt/kit/dist/index.mjs:2119:12)\n at resolveConfig (node_modules/.pnpm/c12@2.0.1_magicast@0.3.5/node_modules/c12/dist/shared/c12.B4fc1S0C.mjs:348:28)\n at async extendConfig (node_modules/.pnpm/c12@2.0.1_magicast@0.3.5/node_modules/c12/dist/shared/c12.B4fc1S0C.mjs:255:21)\n at async loadConfig (node_modules/.pnpm/c12@2.0.1_magicast@0.3.5/node_modules/c12/dist/shared/c12.B4fc1S0C.mjs:187:5)\n at async loadNuxtConfig (node_modules/.pnpm/@nuxt+kit@3.15.0_magicast@0.3.5_rollup@4.29.1/node_modules/@nuxt/kit/dist/index.mjs:2535:18)\n at async Object.run (node_modules/.pnpm/nuxi@3.17.2/node_modules/nuxi/dist/chunks/dev.mjs:170:25)\n at async runCommand$1 (node_modules/.pnpm/nuxi@3.17.2/node_modules/nuxi/dist/shared/nuxi.DSPrE7vg.mjs:1767:16)\n at async runCommand$1 (node_modules/.pnpm/nuxi@3.17.2/node_modules/nuxi/dist/shared/nuxi.DSPrE7vg.mjs:1758:11)\n at async runMain$1 (node_modules/.pnpm/nuxi@3.17.2/node_modules/nuxi/dist/shared/nuxi.DSPrE7vg.mjs:1896:7) \n\n ERROR Cannot read properties of undefined (reading 'options') 2:17:28 PM\n\n ELIFECYCLE Command failed with exit code 1.\n```\n\n### Description\n\n**Actual Output**: The app doesn't start.\n\n**Expected Output**: The app should start properly.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3244,3245],{"name":3135,"color":3136},{"name":3138,"color":3139},3005,"`Cannot read properties of undefined (reading 'options')` when using `@nuxt/ui-pro` v3.0.0-alpha.10","2025-01-25T13:12:12Z","https://github.com/nuxt/ui/issues/3005",0.6825952,{"description":3252,"labels":3253,"number":3255,"owner":3144,"repository":3144,"state":3157,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[3254],{"name":3191,"color":3216},28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.68261844,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZVjMh6DsqIEKIQZhIQIC5dydTWWjOBNJAJNXW54-NiM":-1},"/nuxt/ui/4373"]