` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2079,2082,2085],{"name":2080,"color":2081},"question","d876e3",{"name":2083,"color":2084},"v3","49DCB8",{"name":2086,"color":2087},"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.7137994,{"description":2094,"labels":2095,"number":2099,"owner":1994,"repository":1995,"state":2057,"title":2100,"updated_at":2101,"url":2102,"score":2103},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@10.6.2\n- Builder: -\n- User Config: modules, css, runtimeConfig, uiPro, compatibilityDate, devtools, future, experimental\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/ui-pro@3.0.0, @nuxt/content@3.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```html\n\u003CProsePre lang=\"yaml\">{{ yaml }}\u003C/ProsePre>\n```\n\n\n### Description\n\nMade sure I have content installed and loaded - renders just fine, copy button shows the ✅ - but nothing is copied\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2096,2097,2098],{"name":1985,"color":1986},{"name":2083,"color":2084},{"name":1991,"color":1992},3545,"Clipboard button doesnt copy content when using ProsePre directly","2025-03-13T00:31:04Z","https://github.com/nuxt/ui/issues/3545",0.7158016,{"description":2105,"labels":2106,"number":2110,"owner":1994,"repository":1995,"state":2057,"title":2111,"updated_at":2112,"url":2113,"score":2114},"### 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```",[2107,2108,2109],{"name":1985,"color":1986},{"name":2083,"color":2084},{"name":1991,"color":1992},3004,"ULink make Histoire crash","2025-03-28T17:36:15Z","https://github.com/nuxt/ui/issues/3004",0.7227261,{"description":2116,"labels":2117,"number":2123,"owner":1994,"repository":1994,"state":2057,"title":2124,"updated_at":2125,"url":2126,"score":2127},"### Environment\n\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0-rc.10-27710784.e22bbcc`\r\n- Nitro Version: `0.5.2-27709289.11cc5cd`\r\n- Package Manager: `npm@8.12.1`\r\n- Builder: `vite`\r\n- User Config: `app`, `css`, `build`, `imports`, `modules`, `nitro`, `runtimeConfig`, `typescript`, `vite`\r\n- Runtime Modules: `nuxt-graphql-client@0.1.15`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nCan't reproduce because Stacklblitz doesn't actually show any TS.\n\n### Describe the bug\n\nWhen defining a server api route, it'll autmoatically infer the right return types (yay!), so when calling `const data = $fetch('/api/test')`, `data` can be used safely.\r\n\r\nHowever if you call the API with a query parameter, `const data = $fetch('/api/test?q=hello')`, you will lose all typesafety because the returned type becomes `Promise\u003Cunknown>`.\r\n\r\nI'm not 100% sure why, but maybe because the called URL doesn't match the actual API route due to the added params?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2118,2119,2120,2121],{"name":2051,"color":2052},{"name":2054,"color":2055},{"name":1985,"color":1986},{"name":2122,"color":2070},"🔨 p3-minor",14850,"API route types not correctly inferred when using query params in $fetch","2023-01-19T17:41:08Z","https://github.com/nuxt/nuxt/issues/14850",0.7292357,["Reactive",2129],{},["Set"],["ShallowReactive",2132],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"4PFJzgSVvm3StYiVTYL_jYK2zXcLFLW9Y4i_pBib8k4":-1},"/nuxt/ui/2247"]