",[3150,3153],{"name":3151,"color":3152},"pending triage","E99695",{"name":3154,"color":3155},"needs reproduction","FBCA04",32847,"Incorrect message when updating the version","2025-08-04T07:23:47Z","https://github.com/nuxt/nuxt/issues/32847",0.78774947,{"description":3162,"labels":3163,"number":3169,"owner":3140,"repository":3170,"state":3171,"title":3172,"updated_at":3173,"url":3174,"score":3175},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nsetup fails\r\n\r\n### Additional context\r\n\r\ncc: @tobiasdiez \r\n\r\nHere are the lines\r\n\r\nhttps://github.com/nuxt/test-utils/blob/86d09da23a2d7ba6b0f3dcf2e9ca8c21655a5218/src/core/server.ts#L17-L71\r\n\r\noffending line for me was 57, but could easily be any other lines\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d\r\n\r\nis the offending commit \r\n\r\nspecifically this change\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d#diff-84e9c1e393b43cee97ce99909a2db3a09bf9a2435daa2066b01a838e206edec3\r\n\r\n### Logs\r\n\r\n```shell-script\r\nN/A\r\n```\r\n",[3164,3167],{"name":3165,"color":3166},"bug","d73a4a",{"name":3151,"color":3168},"5D08F5",918,"test-utils","closed","`ctx.nuxt` does not exist when `build: false` in setup","2024-12-05T14:26:41Z","https://github.com/nuxt/test-utils/issues/918",0.70344853,{"description":3177,"labels":3178,"number":3180,"owner":3140,"repository":3170,"state":3171,"title":3181,"updated_at":3182,"url":3183,"score":3184},"### Describe the feature\n\nRight now custom directives are not available when running tests. For example I have a custom uppercase directive and when testing the text field component I get:\r\n```\r\n[Vue warn]: Failed to resolve directive: uppercase\r\n at \u003CMountSuspendedComponent >\r\n at \u003CMountSuspendedHelper>\r\n at \u003CAnonymous ref=\"VTU_COMPONENT\" >\r\n at \u003CVTUROOT>\r\n``` \n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3179],{"name":3151,"color":3168},959,"MountSuspended should consider any directives added to the vue app","2024-10-03T18:02:07Z","https://github.com/nuxt/test-utils/issues/959",0.75009996,{"description":3186,"labels":3187,"number":3197,"owner":3140,"repository":3198,"state":3171,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Description\n\nBreadcrumb uses Link (and LinkBase) to implement the item rendering and navigation. Link (through LinkBase) in itself supports `onClick` event/prop. Now, passing `onClick` to the breadcrumb item does not go all the way through to the LinkBase, and thus prevents the fine-grained control of the Breadcrumb component.\n\nThe usage would look something like this:\n```\n\u003Ctemplate>\n \u003CUBreadcrumb :items=\"items\" />\n\u003C/template>\n\u003Cscript setup>\nconst items = [\n { label: \"click for one\", onClick: () => alert(\"1\"), to: \"/one\" },\n { label: \"click for two\", onClick: () => alert(\"2\"), to: \"/two\" },\n]\n\u003C/script>\n```\n\nMy need is to have some secondary effects happening besides the navigation when the user clicks on a breadcrumb item.\n\n### Additional context\n\n_No response_",[3188,3191,3194],{"name":3189,"color":3190},"enhancement","a2eeef",{"name":3192,"color":3193},"v3","49DCB8",{"name":3195,"color":3196},"triage","ffffff",3631,"ui","Support for `onClick` event on Breadcrumb items","2025-03-24T18:08:16Z","https://github.com/nuxt/ui/issues/3631",0.76050586,{"description":3204,"labels":3205,"number":3213,"owner":3140,"repository":3140,"state":3171,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Environment\n\nChromium Engine Version 107.0.5304.110\n\n### Reproduction\n\nhttps://nuxt.com/docs/getting-started/seo-meta\n\n### Describe the bug\n\nMarkdown render code block badly. Missing colon and question mark.\r\n\r\n\u003Cimg width=\"887\" alt=\"image\" src=\"https://user-images.githubusercontent.com/41265413/202634530-be61a161-227c-4f7a-8f4a-b7e1fd616c5e.png\">\r\n\u003Cimg width=\"448\" alt=\"image\" src=\"https://user-images.githubusercontent.com/41265413/202634544-14f76ad0-990b-40c3-a648-cb2e19a29bd0.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3206,3209,3212],{"name":3207,"color":3208},"documentation","5319e7",{"name":3210,"color":3211},"3.x","29bc7f",{"name":3151,"color":3152},15530,"[docs] markdown render code block badly","2023-01-19T17:53:18Z","https://github.com/nuxt/nuxt/issues/15530",0.7618299,{"description":3219,"labels":3220,"number":3222,"owner":3140,"repository":3198,"state":3171,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.16.0`\r\n- Nuxt Version: `3.13.0`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `bun@1.1.2`\r\n- Builder: `-`\r\n- User Config: `srcDir`, `compatibilityDate`, `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxt/eslint@0.5.5`, `@pinia/nuxt@0.5.4`, `@nuxt/image@1.8.0`\r\n- Build Modules: `-`\r\n\n\n### Version\n\n2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1fp2ap\r\n\r\nplease open Preview in new tab\n\n### Description\n\nI can't change position of UNotifications component because when I pass props it doesn't override tailwind class it just add my classes right to default classes.\r\n\r\nSolution which helped me: \r\nset class which you don't want to unset like this bottom-[unset]\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3221],{"name":3165,"color":3166},2128,"UNotifications position","2024-10-10T10:16:14Z","https://github.com/nuxt/ui/issues/2128",0.7669618,{"description":3228,"labels":3229,"number":3233,"owner":3140,"repository":3140,"state":3171,"title":3234,"updated_at":3235,"url":3236,"score":3237},"\r\ndevelopment has no problem but in production this is what happen need help \r\nthanks\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7211\">#c7211\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3230],{"name":3231,"color":3232},"2.x","d4c5f9",3421,"build error","2023-01-18T16:24:02Z","https://github.com/nuxt/nuxt/issues/3421",0.7673088,{"description":3239,"labels":3240,"number":3242,"owner":3140,"repository":3198,"state":3171,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.14.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.4.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jideye\n\n### Description\n\nI've been trying to add font size to a textarea using Nuxt UI, but I'm having trouble getting it to work. For testing purposes, I've tried almost all available options, but none of them seem to be working.\r\n\r\n``` \r\n\u003CUTextarea\r\n :rows=\"10\"\r\n v-model=\"encoderForm.input\"\r\n placeholder=\"Text to encode\"\r\n :ui=\"{\r\n placeholder: 'text-[40px] text-red-500',\r\n base: 'text-[40px]',\r\n form: 'text-[40px]',\r\n rounded: 'rounded-md text-[40px]',\r\n }\" \r\n/>\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3241],{"name":3165,"color":3166},2273,"Nuxt UI - Textarea font size not working","2024-10-02T14:20:24Z","https://github.com/nuxt/ui/issues/2273",0.76869446,{"description":3248,"labels":3249,"number":3256,"owner":3140,"repository":3198,"state":3171,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.9.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: pnpm@9.0.0\r\n- Builder: -\r\n- User Config: app, runtimeConfig, stripe, devtools, modules, gtag, supabase, imports, i18n, colorMode, vue, vite\r\n- Runtime Modules: @nuxtjs/i18n@8.3.1, @nuxtjs/supabase@1.2.1, @nuxt/ui@2.15.2, nuxt-svgo@4.0.0, nuxt-lodash@2.5.3, nuxt-gtag@2.0.5, @nuxtjs/google-fonts@3.2.0, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxt/image@1.6.0, @vueuse/nuxt@10.9.0, @unlok-co/nuxt-stripe@3.0.0\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\n2.15.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-pqemsg?file=app.vue\r\n\r\n### Description\r\n\r\nWeird behavior with modals on mobile devices(with tap event)\r\nWhen I have modal opened with `prevent-close` attr, I cannot click anything inside modal.\r\nIn element inspection I notice that `touch-action: auto;` adds to clicked elements.\r\n\r\nInitially I noticed this bug on my project.\r\nBy default I have modal opened on the page with prevent close attr, and when I opened another modal, on mobile devices the actions inside second modal were blocked.\r\nBut during creation of reproduction, I've noticed that button don't respond even in the first modal(on mobile device)\r\n\r\nI was able to fix it(in my project), by closing the first modal.\r\nBut it's weird because on desktops everything works fine\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3250,3251,3253],{"name":3165,"color":3166},{"name":3252,"color":3196},"wontfix-v2",{"name":3254,"color":3255},"upstream","78bddb",1746,"On mobile device can't click inside items of modal if multiple are open","2025-03-28T17:57:30Z","https://github.com/nuxt/ui/issues/1746",0.7702609,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEdawnZyrWpMHLZZ_uJLiLiqfqChsDpVKt4AiY4jDZKo":-1},"/nuxt/nuxt.com/639"]