` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2954,2957,2958],{"name":2955,"color":2956},"question","d876e3",{"name":2943,"color":2944},{"name":2959,"color":2960},"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.7159016,{"description":2967,"labels":2968,"number":2972,"owner":2874,"repository":2905,"state":2919,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### 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```",[2969,2970,2971],{"name":2896,"color":2897},{"name":2943,"color":2944},{"name":2902,"color":2903},3004,"ULink make Histoire crash","2025-03-28T17:36:15Z","https://github.com/nuxt/ui/issues/3004",0.721225,{"description":2978,"labels":2979,"number":2984,"owner":2874,"repository":2874,"state":2919,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Describe the feature\n\nHey there! I'm really excited about the new `typedPages` feature. Great work on that one!\r\n\r\nI would like to create composable, for example a `useGetAppLocation`, that essentially returns a resolved url while adding a param that every url in my app needs. Example:\r\n\r\n```ts\r\n// props must be any because we don't have a type for it :/\r\nexport const useGetAppLocation = (props: any) => {\r\n\tconst router = useRouter()\r\n\tconst currentSpaceStore = useCurrentSpaceStore()\r\n\r\n\treturn router.resolve({\r\n\t\t...props,\r\n\t\tparams: {\r\n\t\t\t...props.params,\r\n\t\t\tspaceKey: currentSpaceStore.currentSpaceKey\r\n\t\t}\r\n\t})\r\n}\r\n```\r\n\r\nI would like to type this function, but as far as I can see nuxt doesn't export any types to do so. The `router.resolve()` uses `RouteNameMap`, `RouteLocationAsRelativeTyped`, `RouteLocationResolvedTyped ` and so on.\r\n\r\nIdeally, these types could be used in an application.\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).",[2980,2983],{"name":2981,"color":2982},"enhancement","8DEF37",{"name":2916,"color":2917},21032,"`experimental.typedPages`: Export types to make usable in application","2023-05-24T12:19:35Z","https://github.com/nuxt/nuxt/issues/21032",0.7225339,{"description":2990,"labels":2991,"number":2997,"owner":2874,"repository":2874,"state":2919,"title":2998,"updated_at":2999,"url":3000,"score":3001},"### 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_",[2992,2993,2994,2995],{"name":2871,"color":2872},{"name":2916,"color":2917},{"name":2896,"color":2897},{"name":2996,"color":2932},"🔨 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.72290754,["Reactive",3003],{},["Set"],["ShallowReactive",3006],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4PFJzgSVvm3StYiVTYL_jYK2zXcLFLW9Y4i_pBib8k4":-1},"/nuxt/ui/2247"]