\n \u003C/template>\n \u003C/UPopover>\n\n \u003Csvgo-email>\u003C/svgo-email>\n \u003Csvgo-wechat>\u003C/svgo-wechat>\n \u003Csvgo-phone>\u003C/svgo-phone>\n \u003C/div>\n//layout/default.vue\n \u003CHtml :lang=\"head.htmlAttrs.lang\" :dir=\"head.htmlAttrs.dir\">\n \u003CHead>\n\n\u003C!--\n \u003CTitle>{{ title }}\u003C/Title>\n-->\n \u003Ctemplate v-for=\"link in head.link\" :key=\"link.id\">\n \u003CLink :id=\"link.id\" :rel=\"link.rel\" :href=\"link.href\" :hreflang=\"link.hreflang\" />\n \u003C/template>\n \u003Ctemplate v-for=\"meta in head.meta\" :key=\"meta.id\">\n \u003CMeta :id=\"meta.id\" :property=\"meta.property\" :content=\"meta.content\" />\n \u003C/template>\n \u003C/Head>\n \u003CBody>\n \u003CUApp :toaster=\"{position:'top-center'}\">\n \u003Csys-header >\u003C/sys-header>\n \u003Csys-side>\u003C/sys-side>\n \u003Cslot />\n \u003Csys-footer>\u003C/sys-footer>\n \u003C/UApp>\n \u003C/Body>\n \u003C/Html>\n \u003C/div>\n\n\n### Logs\n\n```shell-script\n\n```",[3020,3023,3026],{"name":3021,"color":3022},"bug","d73a4a",{"name":3024,"color":3025},"needs reproduction","CB47CF",{"name":3027,"color":3028},"v3","49DCB8",2915,"nuxt","ui","closed","a big error about UPopover,popover always show at wrong place","2025-01-25T13:11:46Z","https://github.com/nuxt/ui/issues/2915",0.71815974,{"description":3038,"labels":3039,"number":3047,"owner":3030,"repository":3031,"state":3032,"title":3048,"updated_at":3049,"url":3050,"score":3051},"### Description\n\nHello there! thank you all for this awesome library! I'm using the pro version to leverage the Dashboard components, which have been very useful so far, but I'm currently in need of something like this:\n\n\n\nThe idea is to have a NavBar on top of all DashboardPanels across all pages. As far as I can understand the documentation, both DashboardNavbar and DashboardToolbar can only be used inside of a DashboardPanel, but would it be possible to somehow achieve this without breaking the way that the Dashboard components interact with each other? \n\nIn version 2 I kinda went around by just nesting a DashboardPanel inside of a main one (Placed in the layout file) which the Navbar inside it, and then I placed the `\u003Cslot />` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[3040,3043,3044],{"name":3041,"color":3042},"question","d876e3",{"name":3027,"color":3028},{"name":3045,"color":3046},"pro","5BD3CB",3627,"How to add a persistent Navbar on top of all DashboardPanels inside of a DashboardGroup?","2025-03-19T20:53:14Z","https://github.com/nuxt/ui/issues/3627",0.73592037,{"description":3053,"labels":3054,"number":3057,"owner":3030,"repository":3031,"state":3032,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Environment\n\n- OS: Sonoma 14.6\n- Nuxt 3.15.4\n- Node v20.18.0\n- NuxtUI 3.0.0-alpha.12\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nCreate a new project using the NuxtUI 3 starter `npx nuxi init -t ui3 \u003Cmy-app>`\nPaste code from Pagination example \n\n### Description\n\nI have been trying to get pagination working on the table and cannot seem to get the data in the table to only show current page data. The pagination component displays at the bottom of the page but I see the entire list of items in the array.\n\nI created a new project from scratch using the NuxtUI Starter and used the Table with Pagination example as well and still face the same issue.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3055,3056],{"name":3021,"color":3022},{"name":3027,"color":3028},3311,"Table pagination not working","2025-02-13T16:08:53Z","https://github.com/nuxt/ui/issues/3311",0.7360278,{"description":3063,"labels":3064,"number":3070,"owner":3030,"repository":3031,"state":3032,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.4\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-apha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-forked-jncllj\n\n### Description\n\nRelated : https://github.com/histoire-dev/histoire/issues/702\n\nWhen a component is ULink or uses ULink (ex: UButton), Histoire doesn't work anymore.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nLink.vue:108 Uncaught (in promise) TypeError: Cannot destructure property 'href' of 'undefined' as it is undefined.\n at Link.vue:108:28\n at Proxy.renderFnWithContext (runtime-core.esm-bundler.js?v=896f4f1e:699:13)\n at Proxy.\u003Canonymous> (components.mjs:12:28)\n at renderComponentRoot (runtime-core.esm-bundler.js?v=896f4f1e:6521:16)\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js?v=896f4f1e:5343:46)\n at ReactiveEffect.run (reactivity.esm-bundler.js?v=896f4f1e:198:19)\n at setupRenderEffect (runtime-core.esm-bundler.js?v=896f4f1e:5478:5)\n at mountComponent (runtime-core.esm-bundler.js?v=896f4f1e:5253:7)\n at processComponent (runtime-core.esm-bundler.js?v=896f4f1e:5206:9)\n at patch (runtime-core.esm-bundler.js?v=896f4f1e:4722:11)\n```",[3065,3066,3067],{"name":3021,"color":3022},{"name":3027,"color":3028},{"name":3068,"color":3069},"triage","ffffff",3004,"ULink make Histoire crash","2025-03-28T17:36:15Z","https://github.com/nuxt/ui/issues/3004",0.74011964,{"description":3076,"labels":3077,"number":3083,"owner":3030,"repository":3031,"state":3032,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### Description\n\nI think it would be very cool and helpful if the accordion items could have some drag functionality. I want my users to be able to add links to their account in a accordion form. They should be able to reorder it as well. Not sure if the accordion is the right component to add it or that it could be something on it's own. You might have different thoughts. See https://github.com/nuxt/ui/issues/825\n\n### Additional context\n\n_No response_",[3078,3081,3082],{"name":3079,"color":3080},"enhancement","a2eeef",{"name":3027,"color":3028},{"name":3068,"color":3069},3637,"Add drag behaviour to `accordion`","2025-03-24T17:08:50Z","https://github.com/nuxt/ui/issues/3637",0.7427806,{"description":3089,"labels":3090,"number":3093,"owner":3030,"repository":3031,"state":3032,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Description\n\nIn v3, we seem to have lost any focus indication on Buttons. This looks intentional as I see `focus:outline-hidden` on the base. For a11y and good keyboard navigation, it's best practice to have a visual indication of focus: https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#discernibleandpredictablekeyboardfocus\n\nIt seems we've taken a step backward from v2 in this regard. Was this intentional? Is the intent for users to add their own `focus-visible:*` classes via app config?",[3091,3092],{"name":3041,"color":3042},{"name":3027,"color":3028},3658,"Button Focus Indication","2025-03-24T09:50:12Z","https://github.com/nuxt/ui/issues/3658",0.75073606,{"description":3099,"labels":3100,"number":3108,"owner":3030,"repository":3031,"state":3032,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\n\nNode 22\nNuxt 4\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 modal and a slideover using useModal and useSlideover\n2. create a button **(first button**) that opens the modal with useModal()\n3. create one as well **(second button**) INSIDE! the slideover that opens the same modal with useModal()\n\n### Description\n\nNow open the modal outside the slideover with the **first button**. Thats set an index I suppose.\nBut now if you open the slideover and click the **second button** which opens the same modal, it appears behind the slideover.\n\nBut if you reload the page, open the slideover first and then press the second button without ever pressing the first button to open the modal it appears infront.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3101,3102,3103,3104,3105],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},{"name":3068,"color":3069},{"name":3106,"color":3107},"closed-by-bot","ededed",3079,"Modal and slideover z-index bug","2025-03-25T02:04:49Z","https://github.com/nuxt/ui/issues/3079",0.7541773,{"description":3114,"labels":3115,"number":3122,"owner":3030,"repository":3030,"state":3032,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Describe the feature\n\nWe noticed that if a non-existing route middleware is assigned via `definePageMeta()`, there is no build-time validation:\r\n- build passes\r\n- type-check passes\r\n\r\nBut of course during runtime there is an error. We renamed a lot of middlewares in a big project and had to notice the hard way that we forgot some.\r\n\r\nStackBlitz demo: https://stackblitz.com/edit/github-fyckni?file=pages%2Findex.vue\r\n\r\n- `npm run build`\r\n- `npm run type-check`\r\n\r\n**Feature request:** It would be helpful if the type-check and/or build would fail in this case.\n\n### Additional information\n\n- [ ] 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).",[3116,3119],{"name":3117,"color":3118},"types","2875C3",{"name":3120,"color":3121},"🍰 p2-nice-to-have","0E8A16",27860,"Type-check route middleware assignments","2024-08-26T19:57:59Z","https://github.com/nuxt/nuxt/issues/27860",0.75761807,{"description":3128,"labels":3129,"number":3133,"owner":3030,"repository":3030,"state":3032,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Describe the feature\n\nFor API route we want to be controlled by middlewares (using appMiddleware), I suggest to let the config precise which HTTP method is case behavior could differ (i.e. one route with a GET which need a different middleware than the POST).\n\nTwo suggestion : \n\n1. Put method in the key\n\n```ts\n routeRules: {\n \"GET /user\": {\n appMiddleware: ['auth']\n },\n \"DELETE /user\": {\n appMiddleware: ['auth', 'admin']\n }\n }\n```\n\n3. Put the method in the object\n\n```ts\n routeRules: {\n \"/user\": {\n method: 'GET',\n appMiddleware: {\n GET: ['auth'],\n DELETE: ['auth', 'admin']\n }\n }\n },\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).",[3130],{"name":3131,"color":3132},"pending triage","E99695",30855,"Let precise HTTP method in routeRules for middleware (or more?)","2025-02-04T15:57:51Z","https://github.com/nuxt/nuxt/issues/30855",0.7578448,{"description":3139,"labels":3140,"number":3141,"owner":3030,"repository":3142,"state":3032,"title":3143,"updated_at":3144,"url":3145,"score":3146},"I'm experiencing an issue with my local font awesome pro setup.\n\nI'm using Nuxt UI Pro and the issue looks like it's Nuxt Icon related.\n\n\u003Cimg width=\"1407\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/842b0d0f-7437-44a4-bb8f-1f4bded3ed93\" />\n\n\u003Cimg width=\"1439\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c181ed5c-ed16-468b-907f-6dd4facdd9db\" />\n\nAs you can see, it doesn't work. @benjamincanac from Nuxt UI already mentioned me to use the `i-` syntax: `i-fa-light-caret-right`. This doesn't work as well...\n\nI'm I doing something wrong?\n\nContext: https://github.com/nuxt/ui/issues/2590",[],326,"icon","Custom local icons are not rendering","2024-12-19T20:21:50Z","https://github.com/nuxt/icon/issues/326",0.759456,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyr4bHeF8pqYzMNC5-Ep3b734Pxmm_fK-IlbDrOS4Cuc":-1},"/nuxt/ui/2065"]