``` the ```type=\"text\"``` and ```\u003CUSelect />``` fields match heights, but the ```type=\"search\"``` is the outlier.\n- When NOT using ```\u003CUFormField />```, then the ```type=\"text\"``` field is the outlier. \n\n### Additional context\n\nAs rendered in Dev Tools:\n\n\n\nAfter removing ```type=\"search\"``` in dev tools.\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3019,3022,3025],{"name":3020,"color":3021},"bug","d73a4a",{"name":3023,"color":3024},"v3","49DCB8",{"name":3026,"color":3027},"triage","ffffff",4014,"nuxt","ui","open","Input Fields on ```Safari``` has Mismatched Sizes","2025-04-29T04:28:11Z","https://github.com/nuxt/ui/issues/4014",0.6947014,{"description":3037,"labels":3038,"number":3042,"owner":3029,"repository":3030,"state":3031,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### Environment\n\nThe default input fields when used on small devices (Like my iPhone 12 mini) seemingly render text below 16px causing the browser to zoom when clicking an input field. This doesn't happen on my larger devices as presumably the text renders above 16px.\n\nMight be good to force a minimum text size of 16px to avoid this default behaviour as the workaround otherwise is to override that zoom behaviour, but that could impact accessibility unless the user zooms in manually with their fingers.\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input happens on the official site too for example here on my iPhone 12 mini\n\n### Description\n\ninput field text renders below recommended 16px on small devices causing the screen to zoom when clicking input fields. This occurs on input fields smaller than xl. Granted in my opinion the text looks plenty big at medium and large size but those cause the screen zoom by default\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3039,3040,3041],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4117,"Default text size on input fields too small on small devices causing zoom when clicked (sub 16px?)","2025-05-10T18:34:49Z","https://github.com/nuxt/ui/issues/4117",0.7178948,{"description":3048,"labels":3049,"number":3053,"owner":3029,"repository":3030,"state":3031,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.2.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fragrant-fog-7ck4yf\n\nThe schema specifies that the items within the list must be numbers, and the UForm catches the error (displayed in the UAlert below), but the UInputTag object doesn't display it\n\n\u003Cimg width=\"780\" height=\"220\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9594e307-2f7d-4928-b877-d08795abc4b5\" />\n\n### Description\n\nThe UInputTag element does not correctly render the error text for schema validation errors for pattern matching of the individual items within its array. \n\nIt works fine showing an error about the length of the array, but not about problems for the items within the array.\n\n\u003Cimg width=\"779\" height=\"328\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cf031108-314b-4fd5-9859-cd275b8d3410\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3050,3051,3052],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4573,"UInputTag does not display validation errors for pattern matching","2025-07-22T14:39:33Z","https://github.com/nuxt/ui/issues/4573",0.7251372,{"description":3059,"labels":3060,"number":3064,"owner":3029,"repository":3029,"state":3031,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.13.1\n- Nuxt Version: 3.17.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: ssr, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nI tested a few new nuxt apps to see if they are related to a package or module, but they are not. So you can create a new nuxt project, open the dev server with --host, open an android virtual device (I'm using Pixel 8 API 35) and try to access dev server on virtual device's chrome.\n\n### Describe the bug\n\nWhen I try to open nuxt dev server in android virtual device, after nuxt loading screen there is only a blank page. and that's why I can't test my capacitor app in Android Studio. I am sure this is not related to any capacitor or ionic module because it works for Vue 3 + vite dev server. You can test this new vue 3 vite project and expose the dev server to network via --host. You can check the logs in chrome of host machine. Copy and paste chrome://inspect/#devices to url and inspect the device. You will see net::ERR_CONTENT_LENGTH_MISMATCH.\n\n\n\n\n\n### Additional context\n\nI already tried on different android virtual devices but same errors. I also checked on bluestacks emulator and my phone but there is no problem, even hmr works fine. I tried disabling android studio proxy servers, it had no effect.\n\n\n### Logs\n\n```shell-script\nGET http://192.168.1.5:3000/_nuxt/node_modules/ufo/dist/index.mjs?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nruntime-dom.esm-bundler.js:8 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/@vue/shared/dist/shared.esm-bundler.js?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nindex.mjs:2 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/h3/node_modules/cookie-es/dist/index.mjs?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nindex.mjs:3 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/radix3/dist/index.mjs?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nindex.mjs:7 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/iron-webcrypto/dist/index.js?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nindex.mjs:8 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/node-mock-http/dist/index.mjs?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nrouter.js:6 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/@ionic/vue-router/dist/index.js?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\nruntime-dom.esm-bundler.js:6 \n \n \nGET http://192.168.1.5:3000/_nuxt/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=fc85a5b8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)\n```",[3061],{"name":3062,"color":3063},"pending triage","E99695",32107,"net::ERR_CONTENT_LENGTH_MISMATCH error on android virtual device","2025-05-14T11:57:14Z","https://github.com/nuxt/nuxt/issues/32107",0.7394019,{"description":3070,"labels":3071,"number":3075,"owner":3029,"repository":3030,"state":3031,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### 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```",[3072,3073,3074],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.7396994,{"description":3081,"labels":3082,"number":3093,"owner":3029,"repository":3029,"state":3094,"title":3095,"updated_at":3096,"url":3097,"score":3098},"When upgrading from versions:\n\n“nuxt\": “3.13.2”,\n“@nuxt/image\": ‘^1.8.1’,\n\nto the latest ones, the application stopped running, ubuntu console gives the error free() invalid size and stops execution.\n\nI installed valgrind to track the memory error, it shows this error.\n\nAny help would be greatly appreciated.\n\n\n\n",[3083,3084,3087,3090],{"name":3062,"color":3063},{"name":3085,"color":3086},"upstream","E8A36D",{"name":3088,"color":3089},"needs reproduction","FBCA04",{"name":3091,"color":3092},"possible regression","B90A42",30931,"closed","free() invalid size","2025-02-11T09:20:12Z","https://github.com/nuxt/nuxt/issues/30931",0.729268,{"description":3100,"labels":3101,"number":3105,"owner":3029,"repository":3030,"state":3094,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\n/\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/select-menu#theme\n\n### Description\n\nSize variants should change the text size of the `empty` slot (for example, `xs` variant should change the `emtpy` text size to `xs`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3102,3103,3104],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4377,"SelectMenu size does not change the `emtpy` text size","2025-06-25T14:04:07Z","https://github.com/nuxt/ui/issues/4377",0.7297893,{"description":3111,"labels":3112,"number":3115,"owner":3029,"repository":3030,"state":3094,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: compatibilityDate, future, css, components, modules, runtimeConfig, imports, vite, ssr, ignore\n- Runtime Modules: @nuxt/eslint@1.5.2, @nuxt/image@1.10.0, @vueuse/nuxt@13.5.0, @pinia/nuxt@0.11.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nWhen using the UFormField component, passing the `error` prop using the Boolean attribute shorthand syntax does not work as expected.\n\nThis works correctly:\n\n```vue\n\u003CUFormField :label=\"`总额(${rowData?.marginAsset})`\" size=\"lg\" :error=\"true\" />\n```\n\nHowever, this does not work:\n```vue\n\u003CUFormField :label=\"`总额(${rowData?.marginAsset})`\" size=\"lg\" error />\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3113,3114],{"name":3020,"color":3021},{"name":3023,"color":3024},4496,"Boolean attribute not worked on `UFormField`","2025-07-10T10:04:09Z","https://github.com/nuxt/ui/issues/4496",0.7336169,{"description":3121,"labels":3122,"number":3128,"owner":3029,"repository":3029,"state":3094,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.0`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `nitro`, `runtimeConfig`, `vue`, `app`, `serverMiddleware`, `routes`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nGiven the following plugin - mapbox.client.js\r\n\r\n```\r\nimport mapBox from 'mapbox-gl'\r\n\r\nexport default defineNuxtPlugin(() => {\r\n console.log(\"In mapBox plugin\")\r\n return {\r\n\r\n provide: {\r\n mapBox: mapBox\r\n }\r\n }\r\n })\r\n```\r\n\r\nThe application will work fine using the mapBox plugin or not when running with nuxt dev. However, first building with the following npm script:\r\n\r\n`\"build\": \"NITRO_PRESET=node nuxt build\",`\r\n\r\nThen running with the following script, the application will fail. \r\n\r\n```\r\nconst { handler } = await import('./.output/server/index.mjs')\r\n\r\nimport express from 'express'\r\nvar app = express()\r\nconst port = 3100\r\n\r\napp.use(handler)\r\n\r\napp.listen(port, () => {\r\n console.log(`Example app listening on port ${port}`)\r\n```\r\n\r\nI have seen a couple of different errors in different apps. In a simple hello world app, I see the following in the browser and the component that uses the map fails.\r\n\r\n`Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of \"text/html\". Strict MIME type checking is enforced for module scripts per HTML spec.`\r\n\r\n\r\nIn one of the larger apps, the entire app fails as one of the entry.js files fails with the following:\r\n\r\n```\r\nError: Parse Error: Invalid character in chunk size\r\n at HTTPParser.execute (\u003Canonymous>)\r\n at Socket.socketOnData (node:_http_client:534:22)\r\n at Socket.emit (node:events:513:28)\r\n at addChunk (node:internal/streams/readable:315:12)\r\n at readableAddChunk (node:internal/streams/readable:289:9)\r\n at Socket.Readable.push (node:internal/streams/readable:228:10)\r\n at TCP.onStreamRead (node:internal/stream_base_commons:190:23)\r\n```\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nApplication fails when loading production built scripts when trying to load the mapBox library via a client plugin.\r\n\r\n### Additional context\r\n\r\nThis code worked fine in previous Nuxt release candidates.\r\n\r\n### Logs\r\n\r\n_No response_",[3123,3126,3127],{"name":3124,"color":3125},"3.x","29bc7f",{"name":3062,"color":3063},{"name":3088,"color":3089},15316,"Nuxt RC12 throws error in production built code when providing mapBox library via plugin","2023-01-19T17:48:09Z","https://github.com/nuxt/nuxt/issues/15316",0.73600185,{"description":3134,"labels":3135,"number":3138,"owner":3029,"repository":3029,"state":3094,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-qagkk8\n\n### Describe the bug\n\nHello, \n\nI'm running into an issue where typechecking is no longer working in `nuxt@3.14.1592`. \n\nTo reproduce the issue: \n\n1. In the minimal reproduction stackblitz, open the the terminal \n2. Execute `npm install` (to trigger `nuxt prepare`) \n3. Run the command `npm run check-types` (which is just a wrapper for `nuxt typecheck`) \n\n**Result**: The built-in Nuxt 3 typechecking functionality is broken. When the command from (3) is run, an error is thrown that the search string `\"/supportedTSExtensions = .*(?=;)/\"` is not found. \n\n**Desired behaviour**: I'd like to fix the issue so that typechecking works again. We use this in CI, and it's an important alarm bell for us. \n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\n'Search string not found: \"/supportedTSExtensions = .*(?=;)/\"'\n\n ERROR Command failed with exit code 1: npx -p vue-tsc -p typescript vue-tsc --noEmit 11:35:21 AM\n\n at new ExecaError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:1188:1)\n at getFinalError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:1158:9)\n at makeError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:3638:16)\n at getAsyncResult (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:7867:4)\n at handlePromise (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:7850:17)\n at async Object.run (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/typecheck.mjs:112:9)\n at async runCommand$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1679:16)\n at async runCommand$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1670:11)\n at async runMain$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1808:7)\n```",[3136,3137],{"name":3062,"color":3063},{"name":3091,"color":3092},30154,"Built-in typechecking fails on `nuxt@3.14.1592`","2024-12-05T17:50:54Z","https://github.com/nuxt/nuxt/issues/30154",0.7365528,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHC5p2ZlseOWEcuWrtJFfJkffWf9DsOyI4L0921CpjDw":-1},"/nuxt/nuxt/32615"]