\n```",[2013,2014],{"name":1985,"color":1986},{"name":1988,"color":1989},3517,"How To Style NavigationMenu items","2025-03-14T13:01:49Z","https://github.com/nuxt/ui/issues/3517",0.6829055,{"description":2021,"labels":2022,"number":2025,"owner":1991,"repository":1992,"state":1993,"title":2026,"updated_at":2027,"url":2028,"score":2029},"### Description\n\nHi, I'm having a hard time applying transition to dark / light background.\n\nMy `main.css` file is as follows.\n\nChanging the background color from `slate` to `stone`, for example, works fine.\n\nThe problem is just for the light / dark theme transition.\n\n```\n:root {\n --ui-bg: var(--ui-color-neutral-100);\n}\n\n.dark {\n --ui-bg: var(--ui-color-neutral-900);\n}\n\n@layer base {\n body {\n @apply transition-colors duration-1000;\n }\n}\n```\n\nHere is the function that changes the theme:\n\n```\nconst isDark = computed({\n get() {\n return colorMode.value === 'dark';\n },\n set() {\n colorMode.preference = colorMode.value === 'dark' ? 'light' : 'dark';\n },\n});\n```\n\nAny help would be appreciated, thanks!\n",[2023,2024],{"name":1985,"color":1986},{"name":1988,"color":1989},3645,"Applying transition-colors to light / dark theme","2025-03-21T16:20:57Z","https://github.com/nuxt/ui/issues/3645",0.68425024,{"description":2031,"labels":2032,"number":2035,"owner":1991,"repository":1992,"state":1993,"title":2036,"updated_at":2037,"url":2038,"score":2039},"### Description\n\nHi there,\n\nI'm really curious about how Nuxt UI is handling trailing slashes. In the Nuxt Content repo I can see they are using `ufo` to remove the trailing slashes, but in the Nuxt UI repo I can't find how you get rid of it. Even tho I know you can do these things on Vercel and Netlify, I'm curious how you handle it in Nuxt UI.\n\nIn my case, route.path is returning a path with a trailing slash and breaks my `queryCollection`...\n\n```vue\nconst { data: page } = await useAsyncData(\n `${route.path}/.navigation`,\n async () => {\n return await queryCollection('content').path(route.path).first();\n }\n);\n```",[2033,2034],{"name":1985,"color":1986},{"name":1988,"color":1989},3285,"Trailing slashes","2025-02-10T13:25:12Z","https://github.com/nuxt/ui/issues/3285",0.6858877,{"description":2041,"labels":2042,"number":2048,"owner":1991,"repository":2049,"state":1993,"title":2050,"updated_at":2051,"url":2052,"score":2053},"we'd love to have the nuxt.com docs available in translations for users across the world\n\nalthough this has been a plan for some time, and was indeed the case in nuxt v2, we're still not there with v3 docs\n\nRelated issues: https://github.com/nuxt/nuxt/issues/19926, https://github.com/nuxt/nuxt/issues/21926, https://github.com/nuxt/nuxt/discussions/16054, https://github.com/nuxt/nuxt.com/issues/1448 and https://github.com/nuxt/translations/discussions/4 (private repo - relevant content copied into this issue).\n\n## Key requirements\n\n- needs to be performant and not regress performance of the documentation\n- translations need to remain always in sync, falling back to english text if required\n- needs to allow community contribution\n\n## Translation and sync automation\n\nDocumentation sources currently come from https://github.com/nuxt/nuxt.com, https://github.com/nuxt/nuxt and https://github.com/nuxt/examples. upstream changes need to be localisable, and trigger call for updates for translators, without blocking the documentation.\n\nIt would be nice to consider exploring LLM triggers for translation (see for example the way https://github.com/formkit uses ai in the process of building their documentation website) - at least for 'fallback' content.\n\n👉 See https://github.com/nuxt/nuxt/discussions/29949 for a proposal\n\n## Building a team\n\nWe've had many offers of help for translating the docs, and we'll need to build a team - but first we need to add the infrastructure to make updating translations possible.\n\nSo initially I would love for someone or a small group to take on the task of building up the automation + integration into the [nuxt/nuxt.com](https://github.com/nuxt/nuxt.com) repository, before we move ahead to create a bigger team of translators.",[2043,2045],{"name":2002,"color":2044},"1ad6ff",{"name":2046,"color":2047},"roadmap","ff7a1a",1711,"nuxt.com","internationalisation for nuxt.com","2025-01-18T03:00:02Z","https://github.com/nuxt/nuxt.com/issues/1711",0.6887614,{"description":2055,"labels":2056,"number":2069,"owner":1991,"repository":1991,"state":2070,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.0\r\n- Package Manager: bun@1.0.29\r\n- Builder: -\r\n- User Config: app, devtools, modules, build, sourcemap, runtimeConfig, css, imports\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @unocss/nuxt@0.58.5, @vueuse/nuxt@10.9.0\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\n```\r\nconst { data: testData } = useAsyncData\u003C{ id: 1, name: string }[] | null>('some', () => $fetch('/api/some'))\r\ntype TestDataType = MaybeRef\u003Cany[] | null>\r\ntype TestGeneric\u003CT extends TestDataType> = T extends MaybeRef\u003Cinfer U> ? U : T\r\ntype Test = TestGeneric\u003Ctypeof testData>\r\n```\r\n\r\n\r\n\r\n\n\n### Describe the bug\n\nIt was all fine till yesterday I think,\r\nI ran package updates, then this happenes.\r\nIt also happens on vueuse's some functions.\r\n\r\nAny ref types that goes into generic or function arg throws this error about [RefSymbol]\r\n\r\n```\r\nType 'Ref\u003C{ id: 1; name: string; }[] | null>' does not satisfy the constraint 'TestDataType'.\r\n Property '[RefSymbol]' is missing in type 'Ref\u003C{ id: 1; name: string; }[] | null>' but required in type 'Ref\u003Cany[] | null>'.ts(2344)\r\nreactivity.d.ts(420, 5): '[RefSymbol]' is declared here.\r\n```\n\n### Additional context\n\nI see vue's last update is from 20 hours ago,\r\nso I did \r\nnuxi cleanup\r\nremoved all the caches and lockfile of package manager\r\nremoved node_modules\r\nand re installed with vue 3.4.20,\r\nbut it wasn't fixed.\n\n### Logs\n\n_No response_",[2057,2060,2063,2066],{"name":2058,"color":2059},"3.x","29bc7f",{"name":2061,"color":2062},"pending triage","E99695",{"name":2064,"color":2065},"upstream","E8A36D",{"name":2067,"color":2068},"needs reproduction","FBCA04",26009,"closed","typescript error on Ref type","2024-03-04T10:26:04Z","https://github.com/nuxt/nuxt/issues/26009",0.647367,{"description":2076,"labels":2077,"number":2080,"owner":1991,"repository":1992,"state":2070,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[2078,2079],{"name":2002,"color":2003},{"name":1988,"color":1989},3250,"Use `foo-(--bar)` instead of `foo-[var(--bar)]` for tailwindcss classes","2025-02-07T10:24:17Z","https://github.com/nuxt/ui/issues/3250",0.64896405,{"description":2086,"labels":2087,"number":2093,"owner":1991,"repository":1992,"state":2070,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Description\n\nThere is no way to achieve this with the current API. Adding a initialSlideIndex/currentSlideIndex property would be great.\n\n### Additional context\n\n_No response_",[2088,2089,2090],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2091,"color":2092},"triage","ffffff",3669,"Add ability to programmatically set a UCarousel to a specific slide index","2025-03-24T16:44:54Z","https://github.com/nuxt/ui/issues/3669",0.6612952,{"description":2099,"labels":2100,"number":2103,"owner":1991,"repository":1992,"state":2070,"title":2104,"updated_at":2105,"url":2106,"score":2107},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2101,2102],{"name":1985,"color":1986},{"name":1988,"color":1989},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.6617363,["Reactive",2109],{},["Set"],["ShallowReactive",2112],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"rFCqZmmLnH6J8srcWHmubqkHbVAgXK4FuS1mSjTmj2M":-1},"/nuxt/ui/3827"]