\n\u003C/USelectMenu>\n```\n\n### Additional context\n\n_No response_",[3156,3159,3160],{"name":3157,"color":3158},"enhancement","a2eeef",{"name":3143,"color":3144},{"name":3161,"color":3162},"triage","ffffff",3590,"closed","USelectMenu: Allow to override default button","2025-04-08T10:21:54Z","https://github.com/nuxt/ui/issues/3590",0.6717034,{"description":3170,"labels":3171,"number":3172,"owner":3146,"repository":3173,"state":3164,"title":3174,"updated_at":3175,"url":3176,"score":3177},"If you go to any blog and click `Edit on Github` on aside it will bring you to a 404 on github.\r\n\r\nCode that is incorrect: https://github.com/nuxt/nuxt.com/blob/a9b1e32c93714f23703f12add0f0c17cc518bd2a/pages/blog/%5Bslug%5D.vue#L66\r\n\r\nNeeds to be: \r\n\r\n```\r\nhttps://github.com/nuxt/nuxt.com/edit/main/content/${article.value._file}\r\n```",[],1533,"nuxt.com","blog \"Edit on Github\" url is broke.","2024-03-11T22:23:34Z","https://github.com/nuxt/nuxt.com/issues/1533",0.67392147,{"description":3179,"labels":3180,"number":3185,"owner":3146,"repository":3147,"state":3164,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Environment\n\n\n Operating System: Windows_NT\n Node Version: v20.18.0\n Nuxt Version: 3.13.2\n CLI Version: 3.14.0\n Nitro Version: 2.9.7\n Package Manager: pnpm@9.12.1\n Builder: -\n User Config: -\n Runtime Modules: -\n Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nCannot use v3 on stackblitz so no repo.\n\n### Description\n\nIt looks like `onSelect?(e: Event): void` doesn't work, instead it is `select?(e: Event): void`. \nSpent a good amount of time until I figured it out. :')\nDocs problem only or something else?\n\nOnly tried nav and dropdown menus but this probably happens on all components that have onSelect:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3181,3184],{"name":3182,"color":3183},"bug","d73a4a",{"name":3143,"color":3144},2392,"[NavigationMenu/DropdownMenu etc] 'onSelect' doesn't work, instead it is 'select' only","2024-10-16T09:55:28Z","https://github.com/nuxt/ui/issues/2392",0.68777674,{"description":3191,"labels":3192,"number":3194,"owner":3146,"repository":3147,"state":3164,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[3193],{"name":3157,"color":3158},2398,"Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.69250715,{"description":3200,"labels":3201,"number":3205,"owner":3146,"repository":3146,"state":3164,"title":3206,"updated_at":3207,"url":3208,"score":3209},"How to catch this kind of error? I got this when I hit non-existing route while using `axios-module` Error handler.\r\n\r\n\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1972\">#c1972\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3202],{"name":3203,"color":3204},"2.x","d4c5f9",2248,"Cannot read property 'status' of undefined","2023-01-18T15:43:52Z","https://github.com/nuxt/nuxt/issues/2248",0.6938171,{"description":3211,"labels":3212,"number":3215,"owner":3146,"repository":3147,"state":3164,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: -\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: default\n- Runtime Modules: ../src/module, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n^3.0.0-alpha.9\n\n### Reproduction\n\nNormal Nuxt app setup as mentioned here https://ui3.nuxt.dev/getting-started/installation/nuxt\n- Use latest Nuxt app. \n- Add @tailwindcss 4 with vite and install this @nuxt/ui module and add it to Nuxt app. \n- Add @nuxt/ui import to tailwind css file\n\n### Description\n\n- Components such as UButton displays nicely\n- Components such as Accordion or Drawer fails. \n\nHere's a sample code used in `pages/index.vue` file\n\n```html\n\u003CUButton :ui=\"{ base: 'bg-primary-500' }\" class=\"inline-block\">UButton\u003C/UButton>\n\n \u003CUButton label=\"Show toast\" color=\"secondary\" variant=\"solid\" @click=\"showToast\" />\n\n \u003C!-- \u003CUAccordion :items=\"items\" /> -->\n\n \u003CUDrawer id=\"drawer\">\n \u003CUButton label=\"Open\" color=\"surface\" variant=\"solid\" />\n \u003Ctemplate #content>\n \u003CBaseUiPlaceholder class=\"h-48 m-4\" />\n \u003C/template>\n \u003C/UDrawer>\n```\n\nIf we use Accordion or Drawer (as mentioned in above code), we get 500 Error and app crashes. \n\n\n\nIf we comment out the Accordion and Drawer, no error comes, and app works nicely. \n\n\n\nSee: No error if we don't use the error-causing components. \n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3213,3214],{"name":3182,"color":3183},{"name":3143,"color":3144},2769,"[v3] Error `$setup.useId is not a function` in Accordion, Drawer, etc.","2024-11-26T13:44:15Z","https://github.com/nuxt/ui/issues/2769",0.6950354,{"description":3221,"labels":3222,"number":3225,"owner":3146,"repository":3173,"state":3164,"title":3226,"updated_at":3227,"url":3228,"score":3229},"\n\nhttps://nuxt.com/design-kit",[3223],{"name":3182,"color":3224},"ff281a",1516,"[design kit] Color boxes are broken","2024-03-03T09:33:13Z","https://github.com/nuxt/nuxt.com/issues/1516",0.69551414,{"description":3231,"labels":3232,"number":3237,"owner":3146,"repository":3146,"state":3164,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Version\n\n[v1.4.0](https://github.com/nuxt.js/releases/tag/v1.4.0)\n\n### Reproduction link\n\n[https://github.com/danielsalles/nuxt-bug-asyncData-Axios](https://github.com/danielsalles/nuxt-bug-asyncData-Axios)\n\n### Steps to reproduce\n\nnpm install\nnpm run dev\n\nOpen browser:\nAcess localhost:3000/usingssr\nctrl+f5\n\n\nAcess localhost:3000/usingnossr\nctrl+f5\n\n\n\n\n### What is expected ?\n\nThe answer is correct === /usingnossr\n\n### What is actually happening?\n\nWrong response === /usingssr\n\n### Additional comments?\n\nThis bug is referenced to this question (https://cmty.app/nuxt/nuxt.js/issues/c7224).\n\nI'm basically trying to consume an API and I'm not getting it. If it is HTTP (without SSL) it works normally, but I need SSL enabled.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7225\">#c7225\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3233,3236],{"name":3234,"color":3235},"pending triage","E99695",{"name":3203,"color":3204},3431,"Bug using SSL + $axios modules + asyncData","2023-01-22T15:30:04Z","https://github.com/nuxt/nuxt/issues/3431",0.6956335,{"description":3243,"labels":3244,"number":3247,"owner":3146,"repository":3146,"state":3164,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Version\n\n[v2.3.4](https://github.com/nuxt.js/releases/tag/v2.3.4)\n\n### Reproduction link\n\n[https://github.com/jovanmaric/nuxt-axios-error](https://github.com/jovanmaric/nuxt-axios-error)\n\n### Steps to reproduce\n\nThe reproduction link contains a generated app with the latest Nuxt and the following setup:\n- Custom error layout page\n- axios module\n- nuxt-i18n module \n- axios plugin which throws an error if 404 or 500 or higher error is returned.\n- Express with /api proxy\n\nTo reproduce you should run `yarn dev` and open the console on chrome. \n\n### What is expected ?\n\nThat the error component is injected instead of the original component, removing all the semantics of the original component. \n\n### What is actually happening?\n\n`Uncaught (in promise) TypeError: Cannot read property '_t' of null` while no code of the original component should be ran. \n\n### Additional comments?\n\nThe above error does not only apply to the `created()` method. Leading me to think that the re-render is retriggered on server side, while this shouldn't be when the error component injects itself instead of the original component. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8377\">#c8377\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3245,3246],{"name":3234,"color":3235},{"name":3203,"color":3204},4649,"Nuxt error() does not stop execution of previous component","2024-06-30T09:26:25Z","https://github.com/nuxt/nuxt/issues/4649",0.69834095,["Reactive",3253],{},["Set"],["ShallowReactive",3256],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQkWvLHCLkbRHdbd7JmC0_1gycADyAoLF9_ucIvINmW0":-1},"/nuxt/ui/3101"]